From 353adcfa06753970a2865012e7df461464ea27c7 Mon Sep 17 00:00:00 2001 From: Andrea Hoffer Date: Wed, 24 Feb 2021 15:42:52 -0500 Subject: [PATCH] Adding missing prompts --- .../managing_cloud_provider_credentials/cco-mode-sts.adoc | 2 +- modules/cluster-logging-collector-envvar.adoc | 4 ++-- modules/cluster-logging-collector-pod-location.adoc | 2 +- modules/cluster-logging-deploy-cli.adoc | 6 +++--- modules/cluster-logging-log-store-status-comp.adoc | 2 +- modules/dynamic-provisioning-gluster-definition.adoc | 2 +- modules/machineset-osp-adding-bare-metal.adoc | 2 +- modules/nodes-containers-copying-files-procedure.adoc | 4 ++-- modules/op-release-notes-1-2.adoc | 6 +++--- ...figuring-ingress-cluster-traffic-ingress-controller.adoc | 2 +- .../configuring-ingress-cluster-traffic-load-balancer.adoc | 2 +- 11 files changed, 17 insertions(+), 17 deletions(-) diff --git a/authentication/managing_cloud_provider_credentials/cco-mode-sts.adoc b/authentication/managing_cloud_provider_credentials/cco-mode-sts.adoc index 07854ce263c0..30cb52022d4f 100644 --- a/authentication/managing_cloud_provider_credentials/cco-mode-sts.adoc +++ b/authentication/managing_cloud_provider_credentials/cco-mode-sts.adoc @@ -749,7 +749,7 @@ Error from server (NotFound): secrets "aws-creds" not found .Example command with the Image Registry Operator [source,terminal] ---- -oc get secrets -n openshift-image-registry installer-cloud-credentials -o json | jq -r .data.credentials | base64 -d +$ oc get secrets -n openshift-image-registry installer-cloud-credentials -o json | jq -r .data.credentials | base64 -d ---- + The output should show the role and web identity token that are used by the component and look similar to: diff --git a/modules/cluster-logging-collector-envvar.adoc b/modules/cluster-logging-collector-envvar.adoc index ccc0fe7ed8ab..af92ba91f3e6 100644 --- a/modules/cluster-logging-collector-envvar.adoc +++ b/modules/cluster-logging-collector-envvar.adoc @@ -20,11 +20,11 @@ available environment variables. Set any of the Fluentd environment variables as needed: ---- -oc set env ds/fluentd = +$ oc set env ds/fluentd = ---- For example: ---- -oc set env ds/fluentd BUFFER_SIZE_LIMIT=24 +$ oc set env ds/fluentd BUFFER_SIZE_LIMIT=24 ---- diff --git a/modules/cluster-logging-collector-pod-location.adoc b/modules/cluster-logging-collector-pod-location.adoc index 6d1abf8b1474..0772527739b4 100644 --- a/modules/cluster-logging-collector-pod-location.adoc +++ b/modules/cluster-logging-collector-pod-location.adoc @@ -13,7 +13,7 @@ Run the following command in the `openshift-logging` project: [source,terminal] ---- -$oc get pods --selector component=fluentd -o wide -n openshift-logging +$ oc get pods --selector component=fluentd -o wide -n openshift-logging ---- .Example output diff --git a/modules/cluster-logging-deploy-cli.adoc b/modules/cluster-logging-deploy-cli.adoc index 7b8b3039e1d2..be30ca3af458 100644 --- a/modules/cluster-logging-deploy-cli.adoc +++ b/modules/cluster-logging-deploy-cli.adoc @@ -170,7 +170,7 @@ The Elasticsearch Operator is installed to the `openshift-operators-redhat` Name + [source,terminal] ---- -oc get csv --all-namespaces +$ oc get csv --all-namespaces ---- + .Example output @@ -261,7 +261,7 @@ There should be a Cluster Logging Operator in the `openshift-logging` Namespace. + [source,terminal] ---- -oc get csv -n openshift-logging +$ oc get csv -n openshift-logging ---- + .Example output @@ -440,7 +440,7 @@ You should see several pods for OpenShift Logging, Elasticsearch, Fluentd, and K + [source,terminal] ---- -oc get pods -n openshift-logging +$ oc get pods -n openshift-logging ---- + .Example output diff --git a/modules/cluster-logging-log-store-status-comp.adoc b/modules/cluster-logging-log-store-status-comp.adoc index 630b8ff83b9b..3696a5cb20cd 100644 --- a/modules/cluster-logging-log-store-status-comp.adoc +++ b/modules/cluster-logging-log-store-status-comp.adoc @@ -71,7 +71,7 @@ pod/elasticsearch-cdm-1godmszn-3-f66f7d-zqkz7 + [source,terminal] ---- -oc describe pod elasticsearch-cdm-1godmszn-1-6f8495-vp4lw +$ oc describe pod elasticsearch-cdm-1godmszn-1-6f8495-vp4lw ---- + The output includes the following status information: diff --git a/modules/dynamic-provisioning-gluster-definition.adoc b/modules/dynamic-provisioning-gluster-definition.adoc index 997336dc0069..0089db152287 100644 --- a/modules/dynamic-provisioning-gluster-definition.adoc +++ b/modules/dynamic-provisioning-gluster-definition.adoc @@ -67,7 +67,7 @@ also exist. [source,terminal] ---- -oc create secret generic heketi-secret --from-literal=key= -n --type=kubernetes.io/glusterfs +$ oc create secret generic heketi-secret --from-literal=key= -n --type=kubernetes.io/glusterfs ---- This results in the following configuration: diff --git a/modules/machineset-osp-adding-bare-metal.adoc b/modules/machineset-osp-adding-bare-metal.adoc index fb66a98eb577..ada1af60a255 100644 --- a/modules/machineset-osp-adding-bare-metal.adoc +++ b/modules/machineset-osp-adding-bare-metal.adoc @@ -87,7 +87,7 @@ spec: + [source,terminal] ---- -oc create -v baremetalMachineSet.yaml +$ oc create -v baremetalMachineSet.yaml ---- You can now use bare-metal compute machines in your {product-title} cluster. diff --git a/modules/nodes-containers-copying-files-procedure.adoc b/modules/nodes-containers-copying-files-procedure.adoc index 4ae665b93179..474ed6d00752 100644 --- a/modules/nodes-containers-copying-files-procedure.adoc +++ b/modules/nodes-containers-copying-files-procedure.adoc @@ -36,7 +36,7 @@ use with the `oc rsync` command. + [source,terminal] ---- -oc rsync :/ +$ oc rsync :/ ---- + For example: @@ -63,7 +63,7 @@ $ oc rsync devpod1234:/src /home/user/source .Example output [source,terminal] ---- -oc rsync devpod1234:/src/status.txt /home/user/ +$ oc rsync devpod1234:/src/status.txt /home/user/ WARNING: cannot use rsync: rsync not available in container status.txt ---- diff --git a/modules/op-release-notes-1-2.adoc b/modules/op-release-notes-1-2.adoc index e5bd82ea967a..8c6ac6c9fc6f 100644 --- a/modules/op-release-notes-1-2.adoc +++ b/modules/op-release-notes-1-2.adoc @@ -87,21 +87,21 @@ As a workaround, to remove the `EventListener` and `Pod` CRDs: + [source,terminal] ---- -oc patch el/ -p '{"metadata":{"finalizers":["foregroundDeletion"]}}' --type=merge +$ oc patch el/ -p '{"metadata":{"finalizers":["foregroundDeletion"]}}' --type=merge ---- + For example: + [source,terminal] ---- -oc patch el/github-listener-interceptor -p '{"metadata":{"finalizers":["foregroundDeletion"]}}' --type=merge +$ oc patch el/github-listener-interceptor -p '{"metadata":{"finalizers":["foregroundDeletion"]}}' --type=merge ---- + . Delete the `EventListener` CRD: + [source,terminal] ---- -oc patch crd/eventlisteners.triggers.tekton.dev -p '{"metadata":{"finalizers":[]}}' --type=merge +$ oc patch crd/eventlisteners.triggers.tekton.dev -p '{"metadata":{"finalizers":[]}}' --type=merge ---- * When you run a multi-arch container image task without command specification on an IBM Power Systems (ppc64le) or IBM Z (s390x) cluster, the `TaskRun` resource fails with the following error: diff --git a/networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-ingress-controller.adoc b/networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-ingress-controller.adoc index eb9b0be415e6..24fc79601d82 100644 --- a/networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-ingress-controller.adoc +++ b/networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-ingress-controller.adoc @@ -29,7 +29,7 @@ can reach the cluster. to a user, run the following command: + ---- -oc adm policy add-cluster-role-to-user cluster-admin username +$ oc adm policy add-cluster-role-to-user cluster-admin username ---- * Have an {product-title} cluster with at least one master and at least one node diff --git a/networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-load-balancer.adoc b/networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-load-balancer.adoc index b7911f4e3c07..e92a81618ae4 100644 --- a/networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-load-balancer.adoc +++ b/networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-load-balancer.adoc @@ -28,7 +28,7 @@ can reach the cluster. to a user, run the following command: + ---- -oc adm policy add-cluster-role-to-user cluster-admin username +$ oc adm policy add-cluster-role-to-user cluster-admin username ---- * Have an {product-title} cluster with at least one master and at least one node