You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's a lot of other metrics that are exposed from the API server that we need to get. Probably from the other components as well.
Acceptance Criteria
Ability to bring in all metrics from all components with an exclusion list like the Prometheus agent. Reasoning for the exclusion, we don't want the .*_bucket/histograms since that is a massive amount of data we don't need.
Describe Alternatives
Scraping the endpoints using the agent. This works for the API server because it's publicly accessible using a token. However, the other components hardened against the CIS benchmark must listen on 127.0.0.1 and not the exposed to the network through the node's IP or 0.0.0.0. So that doesn't work for things like the kube scheduler/controller/kubelet.
Description
There's a lot of other metrics that are exposed from the API server that we need to get. Probably from the other components as well.
Acceptance Criteria
Ability to bring in all metrics from all components with an exclusion list like the Prometheus agent. Reasoning for the exclusion, we don't want the .*_bucket/histograms since that is a massive amount of data we don't need.
Describe Alternatives
Scraping the endpoints using the agent. This works for the API server because it's publicly accessible using a token. However, the other components hardened against the CIS benchmark must listen on 127.0.0.1 and not the exposed to the network through the node's IP or 0.0.0.0. So that doesn't work for things like the kube scheduler/controller/kubelet.
Dependencies
Additional context
Estimates
For Maintainers Only or Hero Triaging this bug
Suggested Priority (P1,P2,P3,P4,P5):
Suggested T-Shirt size (S, M, L, XL, Unknown):
The text was updated successfully, but these errors were encountered: