Virtual IPs and Service Proxies states that kube-proxy config is a ConfigMap

[sftim]

This is a Bug Report

Problem:
Virtual IPs and Service Proxies states that you use a ConfigMap to configure kube-proxy.

I don't think that's right. See #36675 (comment) for more details.

Proposed Solution:

• Confirm that the in-tree kube-proxy implementation is configured via a local file.
• Revise the reference page to explain that, although you configure kube-proxy with a file, a cluster operator might set up a DaemonSet to define Pods that run kube-proxy, and people often use a ConfigMap.

If you judge that it's useful to, you could also add a task page about managing the DaemonSet that runs kube-proxy.

Page to Update:
https://kubernetes.io/docs/reference/networking/virtual-ips/

Additional Information:
/language en

Prompted by #36675 (comment)

[sftim]

/triage accepted

[kundan2707]

/sig network

[k8s-triage-robot]

This issue has not been updated in over 1 year, and should be re-triaged.

You can:

• Confirm that this issue is still relevant with /triage accepted (org members only)
• Close this issue with /close

For more details on the triage process, see https://www.kubernetes.dev/docs/guide/issue-triage/

/remove-triage accepted

[sftim]

Looks fixed
/close

OK to reopen it if I was wrong.

[k8s-ci-robot]

@sftim: Closing this issue.

In response to this:

Looks fixed
/close

OK to reopen it if I was wrong.

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.