@@ -274,16 +274,18 @@ nitty-gritty.
274274-->
275275
276276### Overview
277+ This proposal defines a new cluster-scoped` ClusterProperty ` resource for storing
278+ cluster-level metadata. The primary justification is to enable identification of
279+ a cluster and its relevant properties within a cluster set, but there is no
280+ intention to limit general use of ` ClusterProperty ` to multi-cluster scenarios.
281+
277282Each cluster in a ClusterSet must be assigned a unique identifier, that lives at
278- least as long as that cluster is a member of the given ClusterSet, and is
279- must not be changed for that same lifetime. This identifier will be stored in a new
280- cluster-scoped ` ClusterProperty ` CR with the well known name
281- ` cluster.clusterset.k8s.io ` that may be referenced by workloads within the
282- cluster. The identifier must either:
283- - be a valid [ RFC-1123] ( https://tools.ietf.org/html/rfc1123 ) DNS label,
284- - or be composed of two valid [ RFC-1123] ( https://tools.ietf.org/html/rfc1123 )
285- DNS labels separated with a dot. The identifier may be created by an
286- implementation dependent mechanism.
283+ least as long as that cluster is a member of the given ClusterSet, and must not
284+ be changed for that same lifetime. This identifier will be stored in a
285+ ` ClusterProperty ` CR with the well known name ` cluster.clusterset.k8s.io ` that
286+ may be referenced by workloads within the cluster. The identifier must be a valid
287+ [ RFC-1123] ( https://tools.ietf.org/html/rfc1123 ) DNS subdomain, and should be less
288+ than 128 characters in total.
287289
288290While it is a member of a ClusterSet, a cluster must also have an additional
289291` clusterset.k8s.io ClusterProperty ` which describes its current membership. This
@@ -446,14 +448,6 @@ ClusterSet at the same time. Finally, two or more clusters may have the same
446448not; see "Uniqueness" above) * as long as* they both do not have membership in
447449the same ClusterSet.
448450
449- ** Cluster identifier composed of two DNS labels** : If a clusterset includes
450- clusters registered with multiple cluster registries, the value of
451- ` cluster.clusterset.k8s.io ClusterProperty ` may not uniquely identify a cluster
452- within the clusterset. In such case the value of `cluster.clusterset.k8s.io
453- ClusterProperty` may be composed of two DNS labels separated with a dot. The
454- additional DNS label is implementation-dependent and allows the implementation
455- to uniquely identify the cluster registry with which a cluster is registered.
456-
457451#### Property: ` clusterset.k8s.io `
458452
459453Contains an identifier that relates the containing cluster to the ClusterSet in
0 commit comments