OCPBUGS-42701-api: Updated the disableMultiNetwork parameter description

openshift · Jan 15, 2025 · 70a6e5d · 70a6e5d
1 parent 52377f0
commit 70a6e5d
Show file tree

Hide file tree

Showing 12 changed files with 39 additions and 30 deletions.
diff --git a/openapi/generated_openapi/zz_generated.openapi.go b/openapi/generated_openapi/zz_generated.openapi.go
diff --git a/openapi/openapi.json b/openapi/openapi.json
@@ -30306,7 +30306,7 @@
           "type": "boolean"
         },
         "disableMultiNetwork": {
-          "description": "disableMultiNetwork specifies whether or not multiple pod network support should be disabled. If unset, this property defaults to 'false' and multiple network support is enabled.",
+          "description": "disableMultiNetwork defaults to 'false' and this setting enables the pod multi-networking capability. disableMultiNetwork# when set to 'true' at cluster install time does not install the components, typically the Multus CNI and the network-attachment-definition CRD, that enable the pod multi-networking capability. Setting the parameter to 'true' might be useful when you need install third-party CNI plugins, but these plugins are not supported by Red Hat. Changing the parameter value as a postinstallation cluster task has no effect.",
           "type": "boolean"
         },
         "disableNetworkDiagnostics": {

diff --git a/operator/v1/types_network.go b/operator/v1/types_network.go
@@ -79,9 +79,10 @@ type NetworkSpec struct {
 	// +listMapKey=name
 	AdditionalNetworks []AdditionalNetworkDefinition `json:"additionalNetworks,omitempty"`
 
-	// disableMultiNetwork specifies whether or not multiple pod network
-	// support should be disabled. If unset, this property defaults to
-	// 'false' and multiple network support is enabled.
+	// disableMultiNetwork defaults to 'false' and this setting enables the pod multi-networking capability. disableMultiNetwork#
+	// when set to 'true' at cluster install time does not install the components, typically the Multus CNI and the network-attachment-definition CRD,
+	// that enable the pod multi-networking capability. Setting the parameter to 'true' might be useful when you need install third-party CNI plugins,
+	// but these plugins are not supported by Red Hat. Changing the parameter value as a postinstallation cluster task has no effect.
 	DisableMultiNetwork *bool `json:"disableMultiNetwork,omitempty"`
 
 	// useMultiNetworkPolicy enables a controller which allows for

diff --git a/operator/v1/zz_generated.crd-manifests/0000_70_network_01_networks-CustomNoUpgrade.crd.yaml b/operator/v1/zz_generated.crd-manifests/0000_70_network_01_networks-CustomNoUpgrade.crd.yaml
@@ -659,9 +659,10 @@ spec:
                 type: boolean
               disableMultiNetwork:
                 description: |-
-                  disableMultiNetwork specifies whether or not multiple pod network
-                  support should be disabled. If unset, this property defaults to
-                  'false' and multiple network support is enabled.
+                  disableMultiNetwork defaults to 'false' and this setting enables the pod multi-networking capability. disableMultiNetwork#
+                  when set to 'true' at cluster install time does not install the components, typically the Multus CNI and the network-attachment-definition CRD,
+                  that enable the pod multi-networking capability. Setting the parameter to 'true' might be useful when you need install third-party CNI plugins,
+                  but these plugins are not supported by Red Hat. Changing the parameter value as a postinstallation cluster task has no effect.
                 type: boolean
               disableNetworkDiagnostics:
                 default: false

diff --git a/operator/v1/zz_generated.crd-manifests/0000_70_network_01_networks-Default.crd.yaml b/operator/v1/zz_generated.crd-manifests/0000_70_network_01_networks-Default.crd.yaml
@@ -643,9 +643,10 @@ spec:
                 type: boolean
               disableMultiNetwork:
                 description: |-
-                  disableMultiNetwork specifies whether or not multiple pod network
-                  support should be disabled. If unset, this property defaults to
-                  'false' and multiple network support is enabled.
+                  disableMultiNetwork defaults to 'false' and this setting enables the pod multi-networking capability. disableMultiNetwork#
+                  when set to 'true' at cluster install time does not install the components, typically the Multus CNI and the network-attachment-definition CRD,
+                  that enable the pod multi-networking capability. Setting the parameter to 'true' might be useful when you need install third-party CNI plugins,
+                  but these plugins are not supported by Red Hat. Changing the parameter value as a postinstallation cluster task has no effect.
                 type: boolean
               disableNetworkDiagnostics:
                 default: false

diff --git a/...or/v1/zz_generated.crd-manifests/0000_70_network_01_networks-DevPreviewNoUpgrade.crd.yaml b/...or/v1/zz_generated.crd-manifests/0000_70_network_01_networks-DevPreviewNoUpgrade.crd.yaml
@@ -659,9 +659,10 @@ spec:
                 type: boolean
               disableMultiNetwork:
                 description: |-
-                  disableMultiNetwork specifies whether or not multiple pod network
-                  support should be disabled. If unset, this property defaults to
-                  'false' and multiple network support is enabled.
+                  disableMultiNetwork defaults to 'false' and this setting enables the pod multi-networking capability. disableMultiNetwork#
+                  when set to 'true' at cluster install time does not install the components, typically the Multus CNI and the network-attachment-definition CRD,
+                  that enable the pod multi-networking capability. Setting the parameter to 'true' might be useful when you need install third-party CNI plugins,
+                  but these plugins are not supported by Red Hat. Changing the parameter value as a postinstallation cluster task has no effect.
                 type: boolean
               disableNetworkDiagnostics:
                 default: false

diff --git a/...r/v1/zz_generated.crd-manifests/0000_70_network_01_networks-TechPreviewNoUpgrade.crd.yaml b/...r/v1/zz_generated.crd-manifests/0000_70_network_01_networks-TechPreviewNoUpgrade.crd.yaml
@@ -659,9 +659,10 @@ spec:
                 type: boolean
               disableMultiNetwork:
                 description: |-
-                  disableMultiNetwork specifies whether or not multiple pod network
-                  support should be disabled. If unset, this property defaults to
-                  'false' and multiple network support is enabled.
+                  disableMultiNetwork defaults to 'false' and this setting enables the pod multi-networking capability. disableMultiNetwork#
+                  when set to 'true' at cluster install time does not install the components, typically the Multus CNI and the network-attachment-definition CRD,
+                  that enable the pod multi-networking capability. Setting the parameter to 'true' might be useful when you need install third-party CNI plugins,
+                  but these plugins are not supported by Red Hat. Changing the parameter value as a postinstallation cluster task has no effect.
                 type: boolean
               disableNetworkDiagnostics:
                 default: false

diff --git a/...1/zz_generated.featuregated-crd-manifests/networks.operator.openshift.io/AAA_ungated.yaml b/...1/zz_generated.featuregated-crd-manifests/networks.operator.openshift.io/AAA_ungated.yaml
@@ -610,9 +610,10 @@ spec:
                 type: boolean
               disableMultiNetwork:
                 description: |-
-                  disableMultiNetwork specifies whether or not multiple pod network
-                  support should be disabled. If unset, this property defaults to
-                  'false' and multiple network support is enabled.
+                  disableMultiNetwork defaults to 'false' and this setting enables the pod multi-networking capability. disableMultiNetwork#
+                  when set to 'true' at cluster install time does not install the components, typically the Multus CNI and the network-attachment-definition CRD,
+                  that enable the pod multi-networking capability. Setting the parameter to 'true' might be useful when you need install third-party CNI plugins,
+                  but these plugins are not supported by Red Hat. Changing the parameter value as a postinstallation cluster task has no effect.
                 type: boolean
               disableNetworkDiagnostics:
                 default: false

diff --git a/...turegated-crd-manifests/networks.operator.openshift.io/AdditionalRoutingCapabilities.yaml b/...turegated-crd-manifests/networks.operator.openshift.io/AdditionalRoutingCapabilities.yaml
@@ -643,9 +643,10 @@ spec:
                 type: boolean
               disableMultiNetwork:
                 description: |-
-                  disableMultiNetwork specifies whether or not multiple pod network
-                  support should be disabled. If unset, this property defaults to
-                  'false' and multiple network support is enabled.
+                  disableMultiNetwork defaults to 'false' and this setting enables the pod multi-networking capability. disableMultiNetwork#
+                  when set to 'true' at cluster install time does not install the components, typically the Multus CNI and the network-attachment-definition CRD,
+                  that enable the pod multi-networking capability. Setting the parameter to 'true' might be useful when you need install third-party CNI plugins,
+                  but these plugins are not supported by Red Hat. Changing the parameter value as a postinstallation cluster task has no effect.
                 type: boolean
               disableNetworkDiagnostics:
                 default: false

diff --git a/...rated.featuregated-crd-manifests/networks.operator.openshift.io/NetworkLiveMigration.yaml b/...rated.featuregated-crd-manifests/networks.operator.openshift.io/NetworkLiveMigration.yaml
@@ -610,9 +610,10 @@ spec:
                 type: boolean
               disableMultiNetwork:
                 description: |-
-                  disableMultiNetwork specifies whether or not multiple pod network
-                  support should be disabled. If unset, this property defaults to
-                  'false' and multiple network support is enabled.
+                  disableMultiNetwork defaults to 'false' and this setting enables the pod multi-networking capability. disableMultiNetwork#
+                  when set to 'true' at cluster install time does not install the components, typically the Multus CNI and the network-attachment-definition CRD,
+                  that enable the pod multi-networking capability. Setting the parameter to 'true' might be useful when you need install third-party CNI plugins,
+                  but these plugins are not supported by Red Hat. Changing the parameter value as a postinstallation cluster task has no effect.
                 type: boolean
               disableNetworkDiagnostics:
                 default: false

diff --git a/...erated.featuregated-crd-manifests/networks.operator.openshift.io/RouteAdvertisements.yaml b/...erated.featuregated-crd-manifests/networks.operator.openshift.io/RouteAdvertisements.yaml
@@ -626,9 +626,10 @@ spec:
                 type: boolean
               disableMultiNetwork:
                 description: |-
-                  disableMultiNetwork specifies whether or not multiple pod network
-                  support should be disabled. If unset, this property defaults to
-                  'false' and multiple network support is enabled.
+                  disableMultiNetwork defaults to 'false' and this setting enables the pod multi-networking capability. disableMultiNetwork#
+                  when set to 'true' at cluster install time does not install the components, typically the Multus CNI and the network-attachment-definition CRD,
+                  that enable the pod multi-networking capability. Setting the parameter to 'true' might be useful when you need install third-party CNI plugins,
+                  but these plugins are not supported by Red Hat. Changing the parameter value as a postinstallation cluster task has no effect.
                 type: boolean
               disableNetworkDiagnostics:
                 default: false

diff --git a/operator/v1/zz_generated.swagger_doc_generated.go b/operator/v1/zz_generated.swagger_doc_generated.go