procedures: Add new requirement for some objects to have part-of label

modules/administration-guide/partials/proc_configuring-che-to-work-with-external-PostgreSQL.adoc

@@ -20,26 +20,44 @@ $ {orch-cli} create namespace {prod-namespace}
 +
 [subs="+quotes,attributes"]
 ----
-$ {orch-cli} create secret generic <server-database-credentials> \ <1>
---from-literal=user=<database-user> \                            <2>
---from-literal=password=<database-password> \                    <3>
+$ {orch-cli} create secret generic __<server-database-credentials>__ \ <1>
+--from-literal=user=__<database-user>__ \ <2>
+--from-literal=password=__<database-password>__ \ <3>
 -n {prod-namespace}
 ----
 <1> Secret name to store {prod-short} server database credentials
 <2> {prod-short} server database username
 <3> {prod-short} server database password
 
+. Add the required labels to the {prod-short} server database credentials secret:
++
+[subs="+quotes,attributes"]
+----
+$ {orch-cli} label secret __<server-database-credentials>__ \ <1>
+ app.kubernetes.io/part-of=che.eclipse.org -n {prod-namespace}
+----
+<1> Secret name to store {prod-short} server database credentials
+
 . Create a secret to store {identity-provider} database credentials:
 +
 [subs="+quotes,attributes"]
 ----
-$ {orch-cli} create secret generic <identity-database-credentials> \ <1>
---from-literal=password=<identity-database-password> \             <2>
+$ {orch-cli} create secret generic __<identity-database-credentials>__ \ <1>
+--from-literal=password=__<identity-database-password>__ \ <2>
 -n {prod-namespace}
 ----
 <1> Secret name to store {identity-provider} database credentials
 <2> {identity-provider} database password
 
+.  Add the required labels to the {identity-provider} database credentials secret:
++
+[subs="+quotes,attributes"]
+----
+$ {orch-cli} label secret __<identity-database-credentials>__ \ <1>
+app.kubernetes.io/part-of=che.eclipse.org -n {prod-namespace}
+----
+<1> Secret name to store {identity-provider} database credentials
+
 . Deploy {prod} by executing the `{prod-cli}` command with applying a patch. For example:
 +
 [subs="+quotes,+attributes"]

modules/installation-guide/partials/proc_configuring-che-hostname.adoc

@@ -29,15 +29,23 @@ $ {orch-cli} create {orch-namespace} {prod-namespace}
 +
 [subs="+quotes,attributes"]
 ----
-$ {orch-cli} create secret TLS $\{secret} \  <1>
---key $\{key_file} \                       <2>
---cert $\{cert_file} \                     <3>
+$ {orch-cli} create secret TLS __<tls-secret-name>__ \ <1>
+--key __<key-file>__ \ <2>
+--cert __<cert-file>__ \ <3>
 -n {prod-namespace}
 ----
 <1> The TLS secret name
 <2> A file with the private key
 <3> A file with the certificate
 
+. Add the required labels to the secret:
++
+[subs="+quotes,attributes"]
+----
+$ {orch-cli} label secret __<tls-secret-name>__ \ <1>
+app.kubernetes.io/part-of=che.eclipse.org -n {prod-namespace}
+----
+<1> The TLS secret name
 
 . Set the following values in the Custom Resource:
 +

modules/installation-guide/partials/proc_deploying-che-with-support-for-git-repositories-with-self-signed-certificates.adoc

@@ -30,6 +30,14 @@ $ {orch-cli} create configmap che-git-self-signed-cert \
 * Certificate files are typically stored as Base64 ASCII files, such as. `.pem`, `.crt`, `.ca-bundle`. Also, they can be encoded as binary data, for example, `.cer`.  All `Secrets` that hold certificate files should use the Base64 ASCII certificate rather than the binary data certificate.
 ====
 
+. Add the required labels to the ConfigMap:
++
+[subs="+quotes,attributes"]
+----
+$ {orch-cli} label configmap che-git-self-signed-cert \
+app.kubernetes.io/part-of=che.eclipse.org -n {prod-namespace}
+----
+
 . Configure {prod-short} to use self-signed certificates for git repositories:
 +
 Update the `gitSelfSignedCert` property. To do that, execute:

modules/installation-guide/partials/proc_importing-untrusted-tls-certificates-old.adoc

@@ -51,6 +51,7 @@ $ {orch-cli} create configmap ca-certs --from-file=__<certificate-file-path>__ -
 +
 To apply more than one certificate, add another `--from-file=_<certificate-file-path>_` option to the above command.
 
+
 . During the installation process, when creating the `CheCluster` custom resource, configure the right name for the created ConfigMap.
 +
 ====
@@ -102,6 +103,7 @@ $ {orch-cli} create configmap __<config-map-name>__ --from-file=__<certificate-f
 +
 To apply more than one certificate, add another `--from-file=_<certificate-file-path>_` option to the above command.
 
+
 . Configure the {prod-short} installation to use the ConfigMap:
 +
 ====