No InternalDNS and Hostname in node status for k8s 1.29

[jayesh-srivastava]

Issue:
Have observed inconsistent behaviors in CAPG clusters using Kubernetes version 1.28 or below v/s CAPG clusters using Kubernetes version 1.29 with Cloud Controller Manager. The difference appears in Node.status.addresses where Kubernetes 1.28 or below clusters have all InternalIP, InternalDNS and Hostname as opposed to Kubernetes 1.29 clusters who only have InternalIP.

Snippet from cluster using K8s 1.28:

Snippet from cluster using K8s 1.29:

This might create issues for downstream users.

[k8s-ci-robot]

This issue is currently awaiting triage.

If the repository mantainers determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

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.