openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 21:46:22 +01:00
Code Issues Releases Activity

Adding missing prompts

Browse Source
This commit is contained in:
Andrea Hoffer
2021-02-24 15:42:52 -05:00
committed by openshift-cherrypick-robot
parent 4f4724ee24
commit 3b18b2ec7d
11 changed files with 17 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
authentication/managing_cloud_provider_credentials/cco-mode-sts.adoc
View File

@@ -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:

4
modules/cluster-logging-collector-envvar.adoc
View File

@@ -20,11 +20,11 @@ available environment variables.
Set any of the Fluentd environment variables as needed:
----
oc set env ds/fluentd <env-var>=<value>
$ oc set env ds/fluentd <env-var>=<value>
----
For example:
----
oc set env ds/fluentd BUFFER_SIZE_LIMIT=24
$ oc set env ds/fluentd BUFFER_SIZE_LIMIT=24
----

2
modules/cluster-logging-collector-pod-location.adoc
View File

@@ -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

6
modules/cluster-logging-deploy-cli.adoc
View File

@@ -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

2
modules/cluster-logging-log-store-status-comp.adoc
View File

@@ -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:

2
modules/dynamic-provisioning-gluster-definition.adoc
View File

@@ -67,7 +67,7 @@ also exist.
[source,terminal]
----
oc create secret generic heketi-secret --from-literal=key=<password> -n <namespace> --type=kubernetes.io/glusterfs
$ oc create secret generic heketi-secret --from-literal=key=<password> -n <namespace> --type=kubernetes.io/glusterfs
----
This results in the following configuration:

2
modules/machineset-osp-adding-bare-metal.adoc
View File

@@ -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.

4
modules/nodes-containers-copying-files-procedure.adoc
View File

@@ -36,7 +36,7 @@ use with the `oc rsync` command.
+
[source,terminal]
----
oc rsync <local-dir> <pod-name>:/<remote-dir>
$ oc rsync <local-dir> <pod-name>:/<remote-dir>
----
+
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
----

6
modules/op-release-notes-1-2.adoc
View File

@@ -87,21 +87,21 @@ As a workaround, to remove the `EventListener` and `Pod` CRDs:
+
[source,terminal]
----
oc patch el/<eventlistener_name> -p '{"metadata":{"finalizers":["foregroundDeletion"]}}' --type=merge
$ oc patch el/<eventlistener_name> -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:

2
networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-ingress-controller.adoc
View File

@@ -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

2
networking/configuring_ingress_cluster_traffic/configuring-ingress-cluster-traffic-load-balancer.adoc
View File

@@ -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