-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Promote Topology Labels to GA #837
Copy link
Copy link
Open
Labels
kind/api-changeCategorizes issue or PR as related to adding, removing, or otherwise changing an APICategorizes issue or PR as related to adding, removing, or otherwise changing an APIsig/cloud-providerCategorizes an issue or PR as relevant to SIG Cloud Provider.Categorizes an issue or PR as relevant to SIG Cloud Provider.stage/stableDenotes an issue tracking an enhancement targeted for Stable/GA statusDenotes an issue tracking an enhancement targeted for Stable/GA status
Metadata
Metadata
Assignees
Labels
kind/api-changeCategorizes issue or PR as related to adding, removing, or otherwise changing an APICategorizes issue or PR as related to adding, removing, or otherwise changing an APIsig/cloud-providerCategorizes an issue or PR as relevant to SIG Cloud Provider.Categorizes an issue or PR as relevant to SIG Cloud Provider.stage/stableDenotes an issue tracking an enhancement targeted for Stable/GA statusDenotes an issue tracking an enhancement targeted for Stable/GA status
Enhancement Description
The topology labels by cloud providers we apply on nodes have been in "beta" for a very long time. Given their usage across the project we should GA them.
The 3 labels are:
beta.kubernetes.io/instance-typefailure-domain.beta.kubernetes.io/zonefailure-domain.beta.kubernetes.io/regionThey should be renamed to:
node.kubernetes.io/instance-typetopology.kubernetes.io/zonetopology.kubernetes.io/regionWhile keeping backwards compatibility in mind. Changing the label format may also be an option given we have to rename the label key anyways.
Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-cloud-provider/20190215-promoting-cloud-provider-labels.md
Primary contact (assignee):
@andrewsykim
Responsible SIGs:
SIG Cloud Provider, SIG Node
Enhancement target (which target equals to which milestone):