cloud-provider-aws icon indicating copy to clipboard operation
cloud-provider-aws copied to clipboard
verified publisher icon kubernetes

Option to use AZ ID in `topology.kubernetes.io/zone` label

Open superbrothers opened this issue 6 months ago • 4 comments

What would you like to be added:

An option (defaulting to false) in aws-cloud-controller-manager to populate the topology.kubernetes.io/zone label with the Availability Zone ID instead of the zone name.

Why is this needed:

Currently, aws-cloud-controller-manager sets the topology.kubernetes.io/zone label using the zone name (e.g., ap-northeast-1a). However, in clusters composed of EC2 instances from multiple AWS accounts, zone names may not map to the same physical Availability Zone. This leads to incorrect behavior in Kubernetes features that rely on consistent zone labeling.

While support for topology.k8s.aws/zone-id was added in https://github.com/kubernetes/cloud-provider-aws/issues/300, Kubernetes features like Service Traffic Distribution require the use of the standard topology.kubernetes.io/zone label and cannot be configured to use a different label.

/kind feature

superbrothers avatar Jul 02 '25 05:07 superbrothers

This issue is currently awaiting triage.

If cloud-provider-aws contributors 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.

k8s-ci-robot avatar Jul 02 '25 05:07 k8s-ci-robot

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot avatar Sep 30 '25 06:09 k8s-triage-robot

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

k8s-triage-robot avatar Oct 30 '25 07:10 k8s-triage-robot

/remove-lifecycle rotten

superbrothers avatar Oct 31 '25 00:10 superbrothers