remote replication target using the `mc admin bucket remote add` command. For mc releases on or after `RELEASE.2022-12-24T15-21-38Z`, the 
--sync, --health-check and --bandwidth flags can be specified in `mc replicate add|update` command

```

          "interval": "",
          "legendFormat": "Pool: {{pool}} Set: {{set}}",
          "range": true,
          "refId": "A",
          "useBackend": false
        }
      ],
      "title": "Cluster Health Status",
      "type": "stat"
    },
    {
      "datasource": {
        "type": "prometheus",
        "uid": "${DS_PROMETHEUS}"
      },
      "description": "",
      "fieldConfig": {

components, but only worked when those components were local to the API server, and when kube-scheduler and kube-controller-manager exposed unsecured health endpoints. Instead of this API, etcd health is included in the kube-apiserver health check and kube-scheduler/kube-controller-manager health checks can be made directly against those components' health endpoints. ([#93570](https://github.com/kubernetes/kubernetes/pull/93570), [@liggitt](https://github.com/liggitt)) [SIG API Machinery, Apps and Cluster...

- If `ComponentSLIs` feature gate is enabled, then `/metrics/slis` now becomes available on cloud-controller-manager allowing you to scrape health check metrics. ([#113340](https://github.com/kubernetes/kubernetes/pull/113340), [@Richabanker](http...

- kubeadm: use etcd's /health endpoint for a HTTP liveness probe on localhost instead of having a custom health check using etcdctl ([#81385](https://github.com/kubernetes/kubernetes/pull/81385), [@neolit123](https://github.com/neolit123))

	op = strings.Replace(op, "(*peerS3Server)", "s3", 1)
	op = strings.Replace(op, "ClusterCheckHandler", "health.Cluster", 1)
	op = strings.Replace(op, "ClusterReadCheckHandler", "health.ClusterRead", 1)
	op = strings.Replace(op, "LivenessCheckHandler", "health.Liveness", 1)
	op = strings.Replace(op, "ReadinessCheckHandler", "health.Readiness", 1)
	op = strings.Replace(op, "-fm", "", 1)
	return op
}

        this.maxChannels = config.getMaxChannels();
        this.channelCounter = new AtomicInteger(0);
        this.multiChannelEnabled = false;
        
        // Schedule periodic health checks
        scheduler.scheduleAtFixedRate(this::performHealthCheck, 10, 10, TimeUnit.SECONDS);
        
        // Schedule interface discovery

- Kubeadm: modified the etcd static Pod `liveness` and `readiness` probes to use a new etcd `v3.5.3+` HTTP(s) health check endpoint `/health?serializable=true` that allows to track the health of individual etcd members and not fail all members if a single member is not healthy in the etcd cluster. ([#110072](https://github.com/kubernetes/kubernetes/pull/110072), [@neolit123](https://github.com/neolit123))

* fix azure load balancer update dns label issue ([#85329](https://github.com/kubernetes/kubernetes/pull/85329), [@nilo19](https://github.com/nilo19))
* Ensure health probes are created for local traffic policy UDP services on Azure ([#85328](https://github.com/kubernetes/kubernetes/pull/85328), [@nilo19](https://github.com/nilo19))



# v1.14.9

quarkus/extensions/smallrye-health/deployment/pom.xml
	quarkus/core/deployment/pom.xml
	quarkus/extensions/arc/deployment/pom.xml
	quarkus/extensions/vertx-http/deployment/pom.xml
	quarkus/extensions/jsonp/deployment/pom.xml
	quarkus/extensions/smallrye-health/spi/pom.xml
	quarkus/extensions/smallrye-openapi/spi/pom.xml
	quarkus/extensions/smallrye-health/runtime/pom.xml
	quarkus/test-framework/junit5-internal/pom.xml