hattfjelldal.no
haugesund.no
haugiang.vn
haus
hayakawa.yamanashi.jp
hayashima.okayama.jp
hazu.aichi.jp
hb.cldmail.ru
hb.cn
hbo
hdfc
hdfcbank
he.cn
health
health-carereform.com
health.nz
health.vn
healthcare
heavy.jp
heguri.nara.jp
heiyu.space
hekinan.aichi.jp
helioho.st
heliohost.us
help
helsinki
hemne.no
hemnes.no
hemsedal.no

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...

    /**
     * Load balancing strategy for distributing operations across channels
     */
    protected String loadBalancingStrategy;
    /**
     * Interval in milliseconds for checking channel health
     */
    protected int channelHealthCheckInterval;

    // RDMA configuration
    /**
     * Flag indicating whether RDMA transport should be used when available
     */
    protected boolean useRDMA;

- 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))

- 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: 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))

- Removed `/livez` livezchecks for KMS v1 and v2 to ensure KMS health does not cause `kube-apiserver` restart. KMS health checks are still in place as a healthz and readiness checks. ([#120583](https://github.com/kubernetes/kubernetes/pull/120583), [@ritazh](https://github.com/ritazh))

- Added support in the Kubelet for monitoring the health of devices allocated via Dynamic Resource Allocation (DRA) and report it in the `pod.status.containerStatuses.allocatedResourcesStatus` field. This required the DRA plugin to implement the new v1alpha1 `NodeHealth` gRPC service. This feature was controlled...

## Changelog since v1.18.18

## Changes by Kind

### API Change

- We have added a new Priority & Fairness rule that exempts all probes (/readyz, /healthz, /livez) to prevent 
  restarting of "healthy" kube-apiserver instance(s) by kubelet. ([#101114](https://github.com/kubernetes/kubernetes/pull/101114), [@tkashem](https://github.com/tkashem)) [SIG API Machinery]

### Bug or Regression

# Timeout for index operations.
index.index.timeout=3m
# Timeout for bulk index operations.
index.bulk.timeout=3m
# Timeout for delete operations in the index.
index.delete.timeout=3m
# Timeout for index health checks.
index.health.timeout=10m
# Timeout for index indices operations.
index.indices.timeout=1m

# filetype

# Mapping of MIME types to filetype labels for indexing.
index.filetype=\
text/html=html\n\