Remove CRI container and pod statistics without cAdvisor
This commit is contained in:
parent
d19090055a
commit
017c8ffda3
|
@ -221,18 +221,8 @@ For instance, if indexed jobs were used as the basis for a suite of long-running
|
||||||
|
|
||||||
|
|
||||||
For more information, read [Handling Pod and container failures](/docs/concepts/workloads/controllers/job/#handling-pod-and-container-failures) in the Kubernetes documentation.
|
For more information, read [Handling Pod and container failures](/docs/concepts/workloads/controllers/job/#handling-pod-and-container-failures) in the Kubernetes documentation.
|
||||||
|
|
||||||
## CRI container and pod statistics without cAdvisor
|
|
||||||
|
|
||||||
This encompasses two related pieces of work (changes to the kubelet's `/metrics/cadvisor` endpoint and improvements to the replacement _summary_ API).
|
*Corrections*: the feature CRI container and pod statistics without cAdvisor has been removed as it did not make the release.
|
||||||
|
|
||||||
There are two main APIs that consumers use to gather stats about running containers and pods: summary API and `/metrics/cadvisor`. The Kubelet is responsible for implementing the summary API, and cadvisor is responsible for fulfilling `/metrics/cadvisor`.
|
|
||||||
|
|
||||||
This enhances CRI implementations to be able to fulfill all the stats needs of Kubernetes. At a high level, there are two pieces of this:
|
|
||||||
|
|
||||||
- It enhances the CRI API with enough metrics to supplement the pod and container fields in the summary API directly from CRI.
|
|
||||||
|
|
||||||
- It enhances the CRI implementations to broadcast the required metrics to fulfill the pod and container fields in the `/metrics/cadvisor` endpoint.
|
|
||||||
|
|
||||||
## Feature graduations and deprecations in Kubernetes v1.28
|
## Feature graduations and deprecations in Kubernetes v1.28
|
||||||
### Graduations to stable
|
### Graduations to stable
|
||||||
|
|
Loading…
Reference in New Issue