Skip to content

Adding missing prompts #29803

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bergerhoffer merged 1 commit into from
Feb 25, 2021
Merged

Adding missing prompts #29803

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion authentication/managing_cloud_provider_credentials/cco-mode-sts.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
4 changes: 2 additions & 2 deletions modules/cluster-logging-collector-envvar.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 changes: 1 addition & 1 deletion modules/cluster-logging-collector-pod-location.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
6 changes: 3 additions & 3 deletions modules/cluster-logging-deploy-cli.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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
Expand Down Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion modules/cluster-logging-log-store-status-comp.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
2 changes: 1 addition & 1 deletion modules/dynamic-provisioning-gluster-definition.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
2 changes: 1 addition & 1 deletion modules/machineset-osp-adding-bare-metal.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 changes: 2 additions & 2 deletions modules/nodes-containers-copying-files-procedure.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand All @@ -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 changes: 3 additions & 3 deletions modules/op-release-notes-1-2.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
2 changes: 1 addition & 1 deletion ...ess_cluster_traffic/configuring-ingress-cluster-traffic-ingress-controller.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion ..._ingress_cluster_traffic/configuring-ingress-cluster-traffic-load-balancer.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down