You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AWS maps the physical Availability Zones randomly to the Availability Zone names for each AWS account.
if we can add karpenter.k8s.aws/zoneid to Well-Known Labels with the value from http://169.254.169.254/latest/meta-data/placement/availability-zone-id this will be helpful to identify AZ level issues when your apps are running in multiple AWS accounts.
How important is this feature to you?
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
The text was updated successfully, but these errors were encountered:
Description
What problem are you trying to solve?
AWS maps the physical Availability Zones randomly to the Availability Zone names for each AWS account.
if we can add
karpenter.k8s.aws/zoneid
to Well-Known Labels with the value from http://169.254.169.254/latest/meta-data/placement/availability-zone-id this will be helpful to identify AZ level issues when your apps are running in multiple AWS accounts.How important is this feature to you?
The text was updated successfully, but these errors were encountered: