"Communicating with Daemon Pods" section should suggest `internalTrafficPolicy: Local`

[glasser]

This is a Bug Report

Problem:

In https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/#communicating-with-daemon-pods several approaches are suggested for communicating with DaemonSet pods. The last approach is

Service: Create a service with the same Pod selector, and use the service to reach a daemon on a random node. (No way to reach specific node.)

However, I think there is a way to reach a specific node, if the node you're trying to reach is "the node we're connecting from": using internalTrafficPolicy: Local. I think it would be reasonable to link that page from here.

Proposed Solution:

Replace that bullet point with something like:

• Service: Create a service with the same Pod selector, and use the service to reach a daemon on a random node. If you only need to connect to the pods from within your cluster and you want to connect to the pod on the current node, you can use Service Internal Traffic Policy.

I am happy to open a PR for this if folks think it's a good improvement.

Page to Update:
https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/#communicating-with-daemon-pods

[k8s-ci-robot]

This issue is currently awaiting triage.

SIG Docs takes a lead on issue triage for this website, but any Kubernetes member can accept issues by applying the triage/accepted label.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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-sigs/prow repository.

[utkarsh-singh1]

/language en
/sig docs