Fix: Prometheus port issue for pod-identity-webhook service

[Subham-sarkar]

What does this PR introduce?

This PR addresses the issue where port 9999 was missing in the pod-identity-webhook service definition, causing problems with Prometheus scraping.

Why is this change needed?

The missing port 9999 was required for Prometheus to scrape metrics from the pod-identity-webhook service. Without this port, monitoring and metrics collection were incomplete.

How does it address the issue?

This PR modifies the service definition to include port 9999 in the spec.ports section, ensuring that Prometheus can scrape metrics correctly.

Related Issue

Fixes #15946

[k8s-ci-robot]

Hi @Subham-sarkar. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions 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/test-infra repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign johngmyers for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[hakman]

/ok-to-test

[hakman]

W1003 18:23:51.684741   37048 results.go:63] error from apply on /v1, Kind=Service kube-system/pod-identity-webhook:
error from apply: error patching object: Service "pod-identity-webhook" is invalid:
[spec.ports[0].name: Required value, spec.ports[1].name: Required value]

[k8s-ci-robot]

@Subham-sarkar: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-kops-test	43a8f8e	link	true	/test pull-kops-test
pull-kops-e2e-aws-upgrade-k127-ko127-to-klatest-kolatest-many-addons	43a8f8e	link	false	/test pull-kops-e2e-aws-upgrade-k127-ko127-to-klatest-kolatest-many-addons
pull-kops-e2e-k8s-gce-cilium	43a8f8e	link	true	/test pull-kops-e2e-k8s-gce-cilium
pull-kops-kubernetes-e2e-ubuntu-gce-build	43a8f8e	link	true	/test pull-kops-kubernetes-e2e-ubuntu-gce-build

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.

Instructions 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/test-infra repository. I understand the commands that are listed here.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle stale
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs.

This bot triages PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

• Mark this PR as fresh with /remove-lifecycle rotten
• Close this PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten