Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
4 changes: 2 additions & 2 deletions modules/cluster-logging-collector-envvar.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -25,11 +25,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
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
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 @@ -263,7 +263,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 @@ -442,7 +442,7 @@ You should see several pods for Cluster Logging, Elasticsearch, Fluentd, and Kib
+
[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
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/con-sdpolicy-networking.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -41,7 +41,7 @@ OpenShift 4 clusters use NAT Gateways to present a public, static IP for any pub
Customers can determine their public static IP addresses by running a pod on the cluster and then querying an external service. For example:

----
oc run ip-lookup --image=busybox -i -t --restart=Never --rm -- /bin/sh -c "/bin/nslookup
$ oc run ip-lookup --image=busybox -i -t --restart=Never --rm -- /bin/sh -c "/bin/nslookup
----

== Cloud network configuration
Expand Down
4 changes: 2 additions & 2 deletions modules/con-sdpolicy-security.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -34,12 +34,12 @@ To request access to `cluster-admin` on your cluster, please open a Red Hat supp
== Project self-service
All users, by default, have the ability to create, update, and delete their projects. This can be restricted if a member of the `dedicated-admin` group removes the self-provisioner role from authenticated users:
----
oc adm policy remove-cluster-role-from-group self-provisioner system:authenticated:oauth
$ oc adm policy remove-cluster-role-from-group self-provisioner system:authenticated:oauth
----

Restrictions can be reverted by applying:
----
oc adm policy add-cluster-role-to-group self-provisioner system:authenticated:oauth
$ oc adm policy add-cluster-role-to-group self-provisioner system:authenticated:oauth
----

== Regulatory compliance
Expand Down
2 changes: 1 addition & 1 deletion modules/dynamic-provisioning-gluster-definition.adoc
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
4 changes: 2 additions & 2 deletions modules/nodes-containers-copying-files-procedure.adoc
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
----
2 changes: 1 addition & 1 deletion modules/nw-multinetwork-sriov.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -187,7 +187,7 @@ spec:
. Run the following command to create the `sriov-device-plugin` DaemonSet:
+
----
oc create -f sriov-device-plugin.yaml
$ oc create -f sriov-device-plugin.yaml
----

. Create a YAML file for the `sriov-cni` DaemonSet with the following contents:
Expand Down
2 changes: 1 addition & 1 deletion modules/oauth-token-requests.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -29,7 +29,7 @@ running the following command.

[source,terminal]
----
oc get route oauth-openshift -n openshift-authentication -o json | jq .spec.host
$ oc get route oauth-openshift -n openshift-authentication -o json | jq .spec.host
----
====

Expand Down
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
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