Merge pull request #7340 from stolostron/jcberger-16124-use-case-cluster

https://issues.redhat.com/browse/ACM-16124

clusters/cluster_lifecycle/release_image_connected.adoc

@@ -1,14 +1,15 @@
 [#release-images-connected]
 = Maintaining a custom list of release images when connected
 
-You might want to use the same release image for all of your clusters. To simplify, you can create your own custom list of release images that are available when creating a cluster. Complete the following steps to manage your available release images:
+You might want to use the same release image for all of your clusters. To simplify, create your own custom list of release images that are available when creating a cluster. Complete the following steps to manage your available release images:
 
 . Fork the link:https://github.com/stolostron/acm-hive-openshift-releases/tree/backplane-2.7[acm-hive-openshift-releases GitHub].
 
 . Add the YAML files for the images that you want available when you create a cluster. Add the images to the `./clusterImageSets/stable/` or `./clusterImageSets/fast/` directory by using the Git console or the terminal.
 
 . Create a `ConfigMap` in the `multicluster-engine` namespace named `cluster-image-set-git-repo`. See the following example, but replace `2.x` with {mce-version}:
 
++
 [source,yaml]
 ----
 apiVersion: v1
@@ -17,11 +18,18 @@ metadata:
   name: cluster-image-set-git-repo
   namespace: multicluster-engine
 data:
-  gitRepoUrl: <forked acm-hive-openshift-releases repository URL> 
+  gitRepoUrl: <1>
   gitRepoBranch: backplane-<2.x>
   gitRepoPath: clusterImageSets
-  channel: <fast or stable>
+  channel: <2>
+  insecureSkipVerify: <3> 
+  caCerts: <4> 
 ----
+<1> Use the URL you got by forking the `acm-hive-openshift-releases` repository. 
+<2> Choose to use either of the supported values `fast` or `stable`.
+<3> Specify `insecureSkipVerify` to `true` for building the insecure connection. The supported values are `true` or `false`.
+<4> List the certified authority (CA) certificates for building a secure HTTPS connection.
+
 You can retrieve the available YAML files from the main repository by merging changes in to your forked repository with the following procedure:
 
 . Commit and merge your changes to your forked repository.
@@ -31,12 +39,14 @@ You can retrieve the available YAML files from the main repository by merging ch
 After updating the `ConfigMap`, the list of available stable release images updates with the currently available images in about one minute.
 
 . You can use the following commands to list what is available and remove the defaults. Replace `<clusterImageSet_NAME>` with the correct name:
+
 +
+[source,bash] 
 ----
 oc get clusterImageSets
 oc delete clusterImageSet <clusterImageSet_NAME>
 ----
 
-View the list of currently available release images in the console when you are creating a cluster.
+. View the list of currently available release images in the console when you are creating a cluster.
 
 For information regarding other fields available through the `ConfigMap`, view the link:https://github.com/stolostron/cluster-image-set-controller/blob/main/README.md[cluster-image-set-controller GitHub repository README].