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
The flag will tell the operator to skip the irreconcilable fields
validation and let the user update/patch conflictive MCs in the cluster
at his own risk. This feature is specially thought to allow users to add
new nodes in a long standing cluster with newer configuration.
Copy file name to clipboardExpand all lines: openapi/openapi.json
+4
Original file line number
Diff line number
Diff line change
@@ -30550,6 +30550,10 @@
30550
30550
"description": "logLevel is an intent based logging for an overall component. It does not give fine grained control, but it is a simple way to manage coarse grained logging choices that operators have to interpret for their operands.\n\nValid values are: \"Normal\", \"Debug\", \"Trace\", \"TraceAll\". Defaults to \"Normal\".",
30551
30551
"type": "string"
30552
30552
},
30553
+
"machineConfigurationValidationPolicy": {
30554
+
"description": "machineConfigurationValidationPolicy tells the operator how new machine configurations should be validated. Allowed values are Strict, Relaxed, and omitted. DefaultValidationPolicy represents a configuration validation mode chosen by the system. Currently, the default is StrictValidationPolicy. StrictValidationPolicy represents a configuration validation mode that enforces that changes to the rendered MCs are not altering fields outside the supported ones. More info about supported fields: https://docs.redhat.com/en/documentation/openshift_container_platform/latest/html/machine_configuration/machine-config-index#what-can-you-change-with-machine-configs RelaxedValidationPolicy represents a configuration validation mode that does not perform any validation over the fields that cannot be changed. Usage of this mode is discouraged.",
30555
+
"type": "string"
30556
+
},
30553
30557
"managedBootImages": {
30554
30558
"description": "managedBootImages allows configuration for the management of boot images for machine resources within the cluster. This configuration allows users to select resources that should be updated to the latest boot images during cluster upgrades, ensuring that new machines always boot with the current cluster version's boot image. When omitted, this means no opinion and the platform is left to choose a reasonable default, which is subject to change over time. The default for each machine manager mode is All for GCP and AWS platforms, and None for all other platforms.",
// machineConfigurationValidationPolicy tells the operator how new machine configurations should be validated.
61
+
// Allowed values are Strict, Relaxed, and omitted.
62
+
// DefaultValidationPolicy represents a configuration validation mode chosen by the system. Currently, the default
63
+
// is StrictValidationPolicy.
64
+
// StrictValidationPolicy represents a configuration validation mode that enforces that changes to the rendered
65
+
// MCs are not altering fields outside the supported ones.
66
+
// More info about supported fields: https://docs.redhat.com/en/documentation/openshift_container_platform/latest/html/machine_configuration/machine-config-index#what-can-you-change-with-machine-configs
67
+
// RelaxedValidationPolicy represents a configuration validation mode that does not perform any validation over
68
+
// the fields that cannot be changed. Usage of this mode is discouraged.
// StrictValidationPolicy represents a configuration validation mode that enforces that changes to the rendered
86
+
// MCs are not altering fields outside the supported ones.
87
+
// More info about supported fields: https://docs.redhat.com/en/documentation/openshift_container_platform/latest/html/machine_configuration/machine-config-index#what-can-you-change-with-machine-configs
0 commit comments