1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 21:46:22 +01:00
Files
openshift-docs/modules/ossm-validating-operators.adoc
2022-02-16 13:36:46 +00:00

66 lines
1.9 KiB
Plaintext

// Module included in the following assemblies:
// * service_mesh/v2x/-ossm-troubleshooting-istio.adoc
[id="ossm-validating-operators_{context}"]
= Validating Operator installation
//The Operator installation steps include verifying the Operator status in the OpenShift console.
When you install the {ProductName} Operators, OpenShift automatically creates the following objects as part of a successful Operator installation:
* config maps
* custom resource definitions
* deployments
* pods
* replica sets
* roles
* role bindings
* secrets
* service accounts
* services
.From the {product-title} console
You can verify that the Operator pods are available and running by using the {product-title} console.
. Navigate to *Workloads* -> *Pods*.
. Select the `openshift-operators` namespace.
. Verify that the following pods exist and have a status of `running`:
** `istio-operator`
** `jaeger-operator`
** `kiali-operator`
. Select the `openshift-operators-redhat` namespace.
. Verify that the `elasticsearch-operator` pod exists and has a status of `running`.
.From the command line
. Verify the Operator pods are available and running in the `openshift-operators` namespace with the following command:
+
[source,terminal]
----
$ oc get pods -n openshift-operators
----
+
.Example output
[source,terminal]
----
NAME READY STATUS RESTARTS AGE
istio-operator-bb49787db-zgr87 1/1 Running 0 15s
jaeger-operator-7d5c4f57d8-9xphf 1/1 Running 0 2m42s
kiali-operator-f9c8d84f4-7xh2v 1/1 Running 0 64s
----
+
. Verify the Elasticsearch operator with the following command:
+
[source,terminal]
----
$ oc get pods -n openshift-operators-redhat
----
+
.Example output
[source,terminal]
----
NAME READY STATUS RESTARTS AGE
elasticsearch-operator-d4f59b968-796vq 1/1 Running 0 15s
----