From fb75a2e04a4862156284dd3d4652d46bd051758c Mon Sep 17 00:00:00 2001 From: dfitzmau Date: Mon, 13 Jan 2025 09:41:11 +0000 Subject: [PATCH] OCPBUGS-42701: Updated the disableMultiNetwork parameter in Network API doc --- rest_api/operator_apis/network-operator-openshift-io-v1.adoc | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/rest_api/operator_apis/network-operator-openshift-io-v1.adoc b/rest_api/operator_apis/network-operator-openshift-io-v1.adoc index fa0f8c53ad0e..364628a78bc0 100644 --- a/rest_api/operator_apis/network-operator-openshift-io-v1.adoc +++ b/rest_api/operator_apis/network-operator-openshift-io-v1.adoc @@ -105,9 +105,7 @@ otherwise. | `disableMultiNetwork` | `boolean` -| 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. | `disableNetworkDiagnostics` | `boolean`