Update .spec.config api doc to direct users to docs (#2383)

Signed-off-by: Per Goncalves da Silva <[email protected]>
Co-authored-by: Per Goncalves da Silva <[email protected]>

Author: perdasilva

api/v1/clusterextension_types.go

@@ -103,8 +103,8 @@ type ClusterExtensionSpec struct {
 	// a configuration schema. When not specified, the default configuration of the resolved bundle will be used.
 	//
 	// config is validated against a configuration schema provided by the resolved bundle. If the bundle does not provide
-	// a configuration schema the final manifests will be derived on a best-effort basis. More information on how
-	// to configure the bundle should be found in its end-user documentation.
+	// a configuration schema the bundle is deemed to not be configurable. More information on how
+	// to configure bundles can be found in the OLM documentation associated with your current OLM version.
 	//
 	// <opcon:experimental>
 	// +optional

docs/api-reference/olmv1-api-reference.md

@@ -343,7 +343,7 @@ _Appears in:_
 | `serviceAccount` _[ServiceAccountReference](#serviceaccountreference)_ | serviceAccount is a reference to a ServiceAccount used to perform all interactions<br />with the cluster that are required to manage the extension.<br />The ServiceAccount must be configured with the necessary permissions to perform these interactions.<br />The ServiceAccount must exist in the namespace referenced in the spec.<br />serviceAccount is required. |  | Required: \{\} <br /> |
 | `source` _[SourceConfig](#sourceconfig)_ | source is a required field which selects the installation source of content<br />for this ClusterExtension. Selection is performed by setting the sourceType.<br />Catalog is currently the only implemented sourceType, and setting the<br />sourcetype to "Catalog" requires the catalog field to also be defined.<br />Below is a minimal example of a source definition (in yaml):<br />source:<br />  sourceType: Catalog<br />  catalog:<br />    packageName: example-package |  | Required: \{\} <br /> |
 | `install` _[ClusterExtensionInstallConfig](#clusterextensioninstallconfig)_ | install is an optional field used to configure the installation options<br />for the ClusterExtension such as the pre-flight check configuration. |  |  |
-| `config` _[ClusterExtensionConfig](#clusterextensionconfig)_ | config is an optional field used to specify bundle specific configuration<br />used to configure the bundle. Configuration is bundle specific and a bundle may provide<br />a configuration schema. When not specified, the default configuration of the resolved bundle will be used.<br />config is validated against a configuration schema provided by the resolved bundle. If the bundle does not provide<br />a configuration schema the final manifests will be derived on a best-effort basis. More information on how<br />to configure the bundle should be found in its end-user documentation.<br /><opcon:experimental> |  |  |
+| `config` _[ClusterExtensionConfig](#clusterextensionconfig)_ | config is an optional field used to specify bundle specific configuration<br />used to configure the bundle. Configuration is bundle specific and a bundle may provide<br />a configuration schema. When not specified, the default configuration of the resolved bundle will be used.<br />config is validated against a configuration schema provided by the resolved bundle. If the bundle does not provide<br />a configuration schema the bundle is deemed to not be configurable. More information on how<br />to configure bundles can be found in the OLM documentation associated with your current OLM version.<br /><opcon:experimental> |  |  |
 
 
 #### ClusterExtensionStatus

helm/olmv1/base/operator-controller/crd/experimental/olm.operatorframework.io_clusterextensions.yaml

@@ -64,8 +64,8 @@ spec:
                   a configuration schema. When not specified, the default configuration of the resolved bundle will be used.
 
                   config is validated against a configuration schema provided by the resolved bundle. If the bundle does not provide
-                  a configuration schema the final manifests will be derived on a best-effort basis. More information on how
-                  to configure the bundle should be found in its end-user documentation.
+                  a configuration schema the bundle is deemed to not be configurable. More information on how
+                  to configure bundles can be found in the OLM documentation associated with your current OLM version.
                 properties:
                   configType:
                     description: |-

manifests/experimental-e2e.yaml

@@ -964,8 +964,8 @@ spec:
                   a configuration schema. When not specified, the default configuration of the resolved bundle will be used.
 
                   config is validated against a configuration schema provided by the resolved bundle. If the bundle does not provide
-                  a configuration schema the final manifests will be derived on a best-effort basis. More information on how
-                  to configure the bundle should be found in its end-user documentation.
+                  a configuration schema the bundle is deemed to not be configurable. More information on how
+                  to configure bundles can be found in the OLM documentation associated with your current OLM version.
                 properties:
                   configType:
                     description: |-

manifests/experimental.yaml

@@ -929,8 +929,8 @@ spec:
                   a configuration schema. When not specified, the default configuration of the resolved bundle will be used.
 
                   config is validated against a configuration schema provided by the resolved bundle. If the bundle does not provide
-                  a configuration schema the final manifests will be derived on a best-effort basis. More information on how
-                  to configure the bundle should be found in its end-user documentation.
+                  a configuration schema the bundle is deemed to not be configurable. More information on how
+                  to configure bundles can be found in the OLM documentation associated with your current OLM version.
                 properties:
                   configType:
                     description: |-