1. What kops version are you running? The command kops version, will display
this information.
kops 1.29
2. What Kubernetes version are you running? kubectl version will print the
version if a cluster is running or provide the Kubernetes version specified as
a kops flag.
k8s 1.29
3. What cloud provider are you using?
AWS
4. What commands did you run? What is the simplest way to reproduce this issue?
kops update
kops update with kops 1.29 creates a new NLB for the API. However, the DNS records for api.<cluster FQDN> still reference the older LB.
When kops update --prune is applied, the old LB is terminated resulting in non-graceful migration of traffic to the new NLB.
When the first kops update using version 1.29 is used, kops should also update the AliasTarget (R53 record) to point to the DNS name of the newly provisioned NLB once targets are registered.
/kind bug
1. What
kopsversion are you running? The commandkops version, will display this information. kops 1.292. What Kubernetes version are you running?
kubectl versionwill print the version if a cluster is running or provide the Kubernetes version specified as akopsflag. k8s 1.293. What cloud provider are you using? AWS
4. What commands did you run? What is the simplest way to reproduce this issue? kops update
kops update with kops
1.29creates a new NLB for the API. However, the DNS records forapi.<cluster FQDN>still reference the older LB.When
kops update --pruneis applied, the old LB is terminated resulting in non-graceful migration of traffic to the new NLB.When the first
kops updateusing version1.29is used, kops should also update the AliasTarget (R53 record) to point to the DNS name of the newly provisioned NLB once targets are registered.