Skip to content

Commit 3b22ed8

Browse files
committed
update enum names
Signed-off-by: Britania Rodriguez Reyes <[email protected]>
1 parent 59b4a97 commit 3b22ed8

File tree

3 files changed

+22
-22
lines changed

3 files changed

+22
-22
lines changed

apis/placement/v1beta1/clusterresourceplacement_types.go

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

490490
const (
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.

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1675,16 +1675,16 @@ spec:
16751675
minimum: 1
16761676
type: integer
16771677
statusReportingScope:
1678-
default: ClusterScope
1678+
default: ClusterScopeOnly
16791679
description: |-
16801680
StatusReportingScope controls where ClusterResourcePlacement status information is made available.
1681-
When set to "ClusterScope", status is accessible only through the cluster-scoped ClusterResourcePlacement object.
1682-
When set to "NamespaceScope", a ClusterResourcePlacementStatus object is created in the target namespace,
1681+
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,
16831683
providing namespace-scoped access to the placement status alongside the cluster-scoped status.
1684-
Defaults to "ClusterScope".
1684+
Defaults to "ClusterScopeOnly".
16851685
enum:
1686-
- ClusterScope
1687-
- NamespaceScope
1686+
- ClusterScopeOnly
1687+
- ClusterAndNamespaceScope
16881688
type: string
16891689
strategy:
16901690
description: The rollout strategy to use to replace existing placement

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -610,16 +610,16 @@ spec:
610610
minimum: 1
611611
type: integer
612612
statusReportingScope:
613-
default: ClusterScope
613+
default: ClusterScopeOnly
614614
description: |-
615615
StatusReportingScope controls where ClusterResourcePlacement status information is made available.
616-
When set to "ClusterScope", status is accessible only through the cluster-scoped ClusterResourcePlacement object.
617-
When set to "NamespaceScope", a ClusterResourcePlacementStatus object is created in the target namespace,
616+
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,
618618
providing namespace-scoped access to the placement status alongside the cluster-scoped status.
619-
Defaults to "ClusterScope".
619+
Defaults to "ClusterScopeOnly".
620620
enum:
621-
- ClusterScope
622-
- NamespaceScope
621+
- ClusterScopeOnly
622+
- ClusterAndNamespaceScope
623623
type: string
624624
strategy:
625625
description: The rollout strategy to use to replace existing placement

0 commit comments

Comments
 (0)