You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: fleetconfig-controller/charts/fleetconfig-controller/crds/fleetconfig.open-cluster-management.io_spokes.yaml
+9-1Lines changed: 9 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -73,9 +73,17 @@ spec:
73
73
description: CleanupConfig is used to configure which resources should
74
74
be automatically garbage collected during cleanup.
75
75
properties:
76
+
forceClusterDrain:
77
+
default: false
78
+
description: |-
79
+
If set, all ManifestWorks which were created using a Placement will be automatically descheduled from the Spoke cluster during deletion.
80
+
This includes AddOns installed using installStrategy.type=Placements. If an AddOn must stay running to reconcile deletion of other ManifestWorks,
81
+
it should tolerate the `fleetconfig.open-cluster-management.io/workload-cleanup` taint.
82
+
Manually created ManifestWorks will not be affected and must be manually cleaned up for Spoke deletion to proceed.
83
+
type: boolean
76
84
purgeAgentNamespace:
77
85
default: false
78
-
description: If true, the agent will attempt to garbage collect
86
+
description: If set, the agent will attempt to garbage collect
79
87
its own namespace after the spoke cluster is unjoined.
Copy file name to clipboardExpand all lines: fleetconfig-controller/charts/fleetconfig-controller/values.yaml
+3-1Lines changed: 3 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -184,6 +184,7 @@ fleetConfig:
184
184
## @param fleetConfig.spokes[0].cleanupConfig.purgeKlusterletOperator If set, the klusterlet operator will be purged and all open-cluster-management namespaces deleted when the klusterlet is unjoined from its Hub cluster.
185
185
## @param fleetConfig.spokes[0].cleanupConfig.purgeKubeconfigSecret If set, the kubeconfig secret will be automatically deleted after the agent has taken over managing the Spoke.
186
186
## @param fleetConfig.spokes[0].cleanupConfig.purgeAgentNamespace If true, the agent will attempt to garbage collect its own namespace after the spoke cluster is unjoined.
187
+
## @param fleetConfig.spokes[0].cleanupConfig.forceClusterDrain If set, all ManifestWorks which were created using a Placement will be automatically descheduled from the Spoke cluster during deletion. This includes AddOns installed using installStrategy.type=Placements. If an AddOn must stay running to reconcile deletion of other ManifestWorks, it should tolerate the `fleetconfig.open-cluster-management.io/workload-cleanup` taint. Manually created ManifestWorks will not be affected and must be manually cleaned up for Spoke deletion to proceed.
187
188
## @param fleetConfig.spokes[0].kubeconfig.context The context to use in the kubeconfig file. Leave empty to use the current context.
188
189
## @param fleetConfig.spokes[0].kubeconfig.inCluster If set, the kubeconfig will be read from the cluster. Only applicable for same-cluster operations.
189
190
## @param fleetConfig.spokes[0].kubeconfig.secretReference.name The name of the secret.
logger.Info("WARNING: condition does not have the desired status", "type", c.Type, "reason", c.Reason, "message", c.Message, "status", c.Status, "wantStatus", c.WantStatus)
0 commit comments