Merge pull request #48714 from xenolinux/secret-yaml-example

BZ2101861: Add an example YAML file for secrets

Author: ahardin-rh

modules/installation-user-infra-generate-k8s-manifest-ignition.adoc

@@ -391,6 +391,24 @@ spec:
 
 .. Create YAML files for secrets in the `openshift-install` manifests directory that you generated previously. The secrets must be stored using the namespace and secret name defined in the `spec.secretRef` for each `CredentialsRequest` object. The format for the secret data varies for each cloud provider.
 +
+.Sample `secrets.yaml` file:
+[source,yaml]
+----
+apiVersion: v1
+kind: Secret
+metadata:
+    name: ${secret_name}
+    namespace: ${secret_namespace}
+stringData:
+  azure_subscription_id: ${subscription_id}
+  azure_client_id: ${app_id}
+  azure_client_secret: ${client_secret}
+  azure_tenant_id: ${tenant_id}
+  azure_resource_prefix: ${cluster_name}
+  azure_resourcegroup: ${resource_group}
+  azure_region: ${azure_region}
+----
+
 [IMPORTANT]
 ====
 The release image includes `CredentialsRequest` objects for Technology Preview features that are enabled by the `TechPreviewNoUpgrade` feature set. You can identify these objects by their use of the `release.openshift.io/feature-gate: TechPreviewNoUpgrade` annotation.