Skip to content

Commit 20939f1

Browse files
committed
change enum values
Signed-off-by: Britania Rodriguez Reyes <[email protected]>
1 parent 3600b75 commit 20939f1

File tree

3 files changed

+8
-8
lines changed

3 files changed

+8
-8
lines changed

apis/placement/v1beta1/clusterresourceplacement_types.go

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -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.

config/crd/bases/placement.kubernetes-fleet.io_clusterresourceplacements.yaml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1679,13 +1679,13 @@ spec:
16791679
description: |-
16801680
StatusReportingScope controls where ClusterResourcePlacement status information is made available.
16811681
When set to "ClusterScopeOnly", status is accessible only through the cluster-scoped ClusterResourcePlacement object.
1682-
When set to "ClusterAndNamespaceScope", a ClusterResourcePlacementStatus object is created in the target namespace,
1682+
When set to "NamespaceAccessible", a ClusterResourcePlacementStatus object is created in the target namespace,
16831683
providing namespace-scoped access to the placement status alongside the cluster-scoped status. This option is only
16841684
supported when the ClusterResourcePlacement targets exactly one namespace.
16851685
Defaults to "ClusterScopeOnly".
16861686
enum:
16871687
- ClusterScopeOnly
1688-
- ClusterAndNamespaceScope
1688+
- NamespaceAccessible
16891689
type: string
16901690
strategy:
16911691
description: The rollout strategy to use to replace existing placement

config/crd/bases/placement.kubernetes-fleet.io_resourceplacements.yaml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -614,13 +614,13 @@ spec:
614614
description: |-
615615
StatusReportingScope controls where ClusterResourcePlacement status information is made available.
616616
When set to "ClusterScopeOnly", status is accessible only through the cluster-scoped ClusterResourcePlacement object.
617-
When set to "ClusterAndNamespaceScope", a ClusterResourcePlacementStatus object is created in the target namespace,
617+
When set to "NamespaceAccessible", a ClusterResourcePlacementStatus object is created in the target namespace,
618618
providing namespace-scoped access to the placement status alongside the cluster-scoped status. This option is only
619619
supported when the ClusterResourcePlacement targets exactly one namespace.
620620
Defaults to "ClusterScopeOnly".
621621
enum:
622622
- ClusterScopeOnly
623-
- ClusterAndNamespaceScope
623+
- NamespaceAccessible
624624
type: string
625625
strategy:
626626
description: The rollout strategy to use to replace existing placement

0 commit comments

Comments
 (0)