cluster-api-provider-gcp icon indicating copy to clipboard operation
cluster-api-provider-gcp copied to clipboard

Published 20 hours ago • verified publisher icon kubernetes-sigs

No InternalDNS and Hostname in node status for k8s 1.29

Open jayesh-srivastava opened this issue 4 months ago • 1 comments

/kind bug

What steps did you take and what happened: 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. This might create issues for downstream users.

What did you expect to happen: Expected the Node.status.addresses to have all three types of addresses.

Anything else you would like to add: Snippet from cluster using K8s 1.28: Screenshot 2024-10-18 at 17 48 37

Snippet from cluster using K8s 1.29: Screenshot 2024-10-18 at 17 49 04

Environment:

  • Cluster-api version:
  • Minikube/KIND version:
  • Kubernetes version: (use kubectl version):
  • OS (e.g. from /etc/os-release):

jayesh-srivastava avatar Oct 18 '24 12:10 jayesh-srivastava