aws: Add metrics port 9999 to pod-identity-webhook Service - #18579
kubernetes-prow[bot] merged 1 commit into
Conversation
The pod-identity-webhook Service is annotated with prometheus.io/port: "9999", but that port was missing from the Service spec, so Prometheus could not scrape metrics through the Service. The webhook container serves HTTP /metrics on port 9999 by default (--metrics-port), so expose that port on the Service instead of changing the annotation. Both ports are now named, as required for multi-port Services.
c2f4dbd to
9a98a2b
Compare
|
@hakman: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rifelpet The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
cbcd29a
into
kubernetes:master
The pod-identity-webhook Service is annotated with prometheus.io/port: "9999", but that port was missing from the Service spec, so Prometheus could not scrape metrics through the Service. The webhook container serves HTTP /metrics on port 9999 by default (--metrics-port), so expose that port on the Service instead of changing the annotation. Both ports are now named, as required for multi-port Services.
Fixes #15946