Start using status.hostIP in k8s daemonsets examples

[klingerf]

First reported by @dlaidlaw.

As of Kubernetes 1.7 (kubernetes/kubernetes#42717), we can now retrieve the host IP directly from the downward API via the status.hostIP field, without needing to rely on the spec.nodeName field, which isn't addressable in all Kubernetes environments (including minikube -- #130).

We should update our example configs in this repo to start using status.hostIP instead of spec.nodeName, but we also need to figure out a way to ensure backwards compatibility with older versions of Kubernetes, either by versioning the config files or doing something smarter with environment variable fallback.

[zyf0330]

I have a question, how does status.hostIP choose if there are several internal ips?

[dlaidlaw]

@zyf0330 I believe this done in the cloud-provider code. Each cloud provider (aws, gce, etc) is responsible for providing the instance metadata. In the case of AWS, the the address would come from the aws instance metadata.

[zyf0330]

I just want to set k8s manually not upon the cloud provider node. I have not tried it yet and want to get some info here.

…

On Wed, Mar 28, 2018, 20:47 Don Laidlaw ***@***.***> wrote: @zyf0330 <https://github.com/zyf0330> I believe this done in the cloud-provider code. Each cloud provider (aws, gce, etc) is responsible for providing the instance metadata. In the case of AWS, the the address would come from the aws instance metadata. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#184 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALZ5gU_aoCfB8TVwvA6E4WtYButWk08Pks5ti4ZvgaJpZM4P0gzY> .