ClusterID for ClusterSet identification

[lauralorenz]

Enhancement Description

• One-line enhancement description (can be used as a release note): Introduce the concept of a cluster ID to allow unique identification of clusters within a ClusterSet.
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/tree/master/keps/sig-multicluster/2149-clusterid
• Discussion Link: https://docs.google.com/document/d/1S0u6xzP2gcJKPipA6tBNDNuid76nVKeGhTk7PrCIuQY
• Primary contact (assignee): @lauralorenz
• Responsible SIGs: sig-multicluster
• Enhancement target (which target equals to which milestone):
  • Alpha release target (x.y): TK
  • Beta release target (x.y):
  • Stable release target (x.y):
• Alpha
  • KEP (k/enhancements) update PR(s): TK
  • Code (k/k) update PR(s):
  • Docs (k/website) update PR(s):

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[lauralorenz]

/sig multicluster

[Fei-Guo]

@lauralorenz
I have a use case that does need this feature. It is part of the virtualcluster project hosted in Multi-tenancy WG and the CAPN (in the future). I am currently implementing a namespace scheduler which assigns the tenant namespaces to different super clusters. There is a syncer controller running in each super cluster that watches for the scheduling results in the tenant cluster(the results are stored in tenant namespace annotations with the cluster ID). If the cluster ID in the scheduling result matches the syncer's running cluster ID, the namespace will be synchronized to the cluster. I am currently using a configMap in the super cluster to store the manually set cluster ID of the cluster so that the scheduler and the syncer can find the same cluster identification. A formal CRD is preferable in this case.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[lauralorenz]

/remove-lifecycle stale

[k8s-triage-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[lauralorenz]

/remove-lifecycle stale