@@ -150,12 +150,12 @@ type PlacementSpec struct {
150150 RevisionHistoryLimit * int32 `json:"revisionHistoryLimit,omitempty"`
151151
152152 // StatusReportingScope controls where ClusterResourcePlacement status information is made available.
153- // When set to "ClusterScope ", status is accessible only through the cluster-scoped ClusterResourcePlacement object.
154- // When set to "NamespaceScope ", a ClusterResourcePlacementStatus object is created in the target namespace,
153+ // 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,
155155 // providing namespace-scoped access to the placement status alongside the cluster-scoped status.
156- // Defaults to "ClusterScope ".
157- // +kubebuilder:default=ClusterScope
158- // +kubebuilder:validation:Enum=ClusterScope;NamespaceScope
156+ // Defaults to "ClusterScopeOnly ".
157+ // +kubebuilder:default=ClusterScopeOnly
158+ // +kubebuilder:validation:Enum=ClusterScopeOnly;ClusterAndNamespaceScope
159159 // +kubebuilder:validation:Optional
160160 StatusReportingScope StatusReportingScope `json:"statusReportingScope,omitempty"`
161161}
@@ -489,14 +489,14 @@ type StatusReportingScope string
489489
490490const (
491491
492- // ClusterScope makes status available only through the cluster-scoped ClusterResourcePlacement object.
492+ // ClusterScopeOnly makes status available only through the cluster-scoped ClusterResourcePlacement object.
493493 // This is the default behavior where status information is accessible only to users with cluster-level permissions.
494- ClusterScope StatusReportingScope = "ClusterScope "
494+ ClusterScopeOnly StatusReportingScope = "ClusterScopeOnly "
495495
496- // NamespaceScope makes status available in both cluster and namespace scopes.
497- // In addition to the default cluster-scoped status, a ClusterResourcePlacementStatus object is created
496+ // ClusterAndNamespaceScope makes status available in both cluster and namespace scopes.
497+ // In addition to the cluster-scoped status, a ClusterResourcePlacementStatus object is created
498498 // in the target namespace, enabling namespace-scoped users to access placement status information.
499- NamespaceScope StatusReportingScope = "NamespaceScope "
499+ ClusterAndNamespaceScope StatusReportingScope = "ClusterAndNamespaceScope "
500500)
501501
502502// RolloutStrategy describes how to roll out a new change in selected resources to target clusters.
0 commit comments