@@ -151,12 +151,12 @@ type PlacementSpec struct {
151151
152152 // StatusReportingScope controls where ClusterResourcePlacement status information is made available.
153153 // When set to "ClusterScopeOnly", status is accessible only through the cluster-scoped ClusterResourcePlacement object.
154- // When set to "ClusterAndNamespaceScope ", a ClusterResourcePlacementStatus object is created in the target namespace,
154+ // When set to "NamespaceAccessible ", a ClusterResourcePlacementStatus object is created in the target namespace,
155155 // providing namespace-scoped access to the placement status alongside the cluster-scoped status. This option is only
156156 // supported when the ClusterResourcePlacement targets exactly one namespace.
157157 // Defaults to "ClusterScopeOnly".
158158 // +kubebuilder:default=ClusterScopeOnly
159- // +kubebuilder:validation:Enum=ClusterScopeOnly;ClusterAndNamespaceScope
159+ // +kubebuilder:validation:Enum=ClusterScopeOnly;NamespaceAccessible
160160 // +kubebuilder:validation:Optional
161161 StatusReportingScope StatusReportingScope `json:"statusReportingScope,omitempty"`
162162}
@@ -495,10 +495,10 @@ const (
495495 // This is the default behavior where status information is accessible only to users with cluster-level permissions.
496496 ClusterScopeOnly StatusReportingScope = "ClusterScopeOnly"
497497
498- // ClusterAndNamespaceScope makes status available in both cluster and namespace scopes.
498+ // NamespaceAccessible makes status available in both cluster and namespace scopes.
499499 // In addition to the cluster-scoped status, a ClusterResourcePlacementStatus object is created
500500 // in the target namespace, enabling namespace-scoped users to access placement status information.
501- ClusterAndNamespaceScope StatusReportingScope = "ClusterAndNamespaceScope "
501+ NamespaceAccessible StatusReportingScope = "NamespaceAccessible "
502502)
503503
504504// RolloutStrategy describes how to roll out a new change in selected resources to target clusters.
0 commit comments