Merge pull request #7238 from stolostron/2.9_stage

2.9 refresh

clusters/release_notes/known_issues.adoc

@@ -176,6 +176,12 @@ If this problem occurs, it is typically on the following versions of {ocp-short}
 
 To avoid this error, upgrade your {ocp-short} to version 4.8.18 or later, or 4.9.7 or later.
 
+[#boot-discovey-auto-add-host]
+=== Cannot use host inventory to boot with the discovery image and add hosts automatically
+//2.12:ACM-14719
+
+You cannot use a host inventory, or `InfraEnv` custom resource, to both boot with the discovery image and add hosts automatically. If you used your previous `InfraEnv` resource for the `BareMetalHost` resource, and you want to boot the image yourself, you can work around the issue by creating a new `InfraEnv` resource.
+
 [#cluster-local-offline-reimport]
 === Local-cluster status offline after reimporting with a different name
 //2.4:16977

networking/submariner/subm_disconnected.adoc

@@ -6,21 +6,16 @@ Deploying Submariner on disconnected clusters can help with security concerns by
 [#configuring-submariner-disconnected]
 == Configuring Submariner on disconnected clusters
 
-After following the steps outlined in link:../../install/install_disconnected.adoc#install-on-disconnected-networks[Install in disconnected network environments], you must configure Submariner during the installation to support deployment on disconnected clusters. See the following topics:
+After completing the steps in link:../../install/install_disconnected.adoc#install-on-disconnected-networks[Install in disconnected network environments], configure Submariner during the installation to support deployment on disconnected clusters. 
 
-[#mirroring-images]
-=== Mirroring images in the local registry
+Complete the following steps:
 
-Make sure to mirror the `Submariner Operator bundle` image in the local registry before deploying Submariner on disconnected clusters.
+. Mirror the `Submariner Operator bundle` image in the local registry before you deploy Submariner on disconnected clusters.
 
-[#customizing-catalogsource-names]
-=== Customizing _catalogSource_ names
+. Choose the Submariner Operator version that is compatible with your {acm-short} version. For instance, use `0.16.0` for {acm-short} version 2.9.
 
-By default, `submariner-addon` searches for a `catalogSource` with the name `redhat-operators`. When using a `catalogSource` with a different name, you must update the value of the `SubmarinerConfig.Spec.subscriptionConfig.Source` parameter in the `SubmarinerConfig` associated with your managed cluster with the custom name of the `catalogSource`.
+. Customize `catalogSource` names. By default, `submariner-addon` searches for a `catalogSource` with the name `redhat-operators`. When you use a `catalogSource` with a different name, you must update the value of the `SubmarinerConfig.Spec.subscriptionConfig.Source` parameter in the `SubmarinerConfig` associated with your managed cluster with the custom name of the `catalogSource`.
 
-[#enabling-airgappeddeployment-submarinerconfig]
-=== Enabling _airGappedDeployment_ in _SubmarinerConfig_
+. Enable `airGappedDeployment` in `SubmarinerConfig`.When installing `submariner-addon` on a managed cluster from the {acm} console, you can select the *Disconnected cluster* option so that Submariner does not make API queries to external servers.
 
-When installing `submariner-addon` on a managed cluster from the {acm} console, you can select the *Disconnected cluster* option so that Submariner does not make API queries to external servers.
-
-If you are installing Submariner by using the APIs, you must set the `airGappedDeployment` parameter to `true` in the `SubmarinerConfig` associated with your managed cluster. 
+*Note:* If you are installing Submariner by using the APIs, you must set the `airGappedDeployment` parameter to `true` in the `SubmarinerConfig` associated with your managed cluster.