mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
152 lines
5.5 KiB
Plaintext
152 lines
5.5 KiB
Plaintext
// Module included in the following assemblies:
|
|
// * service_mesh/v2x/-ossm-troubleshooting-istio.adoc
|
|
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="ossm-validating-smcp_{context}"]
|
|
= Validating the Service Mesh control plane installation
|
|
|
|
When you create the {SMProductShortName} control plane, the {SMProductShortName} Operator uses the parameters that you have specified in the `ServiceMeshControlPlane` resource file to do the following:
|
|
|
|
* Creates the Istio components and deploys the following pods:
|
|
** `istiod`
|
|
** `istio-ingressgateway`
|
|
** `istio-egressgateway`
|
|
** `grafana`
|
|
** `prometheus`
|
|
* Calls the Kiali Operator to create Kaili deployment based on configuration in either the SMCP or the Kiali custom resource.
|
|
+
|
|
[NOTE]
|
|
====
|
|
You view the Kiali components under the Kiali Operator, not the {SMProductShortName} Operator.
|
|
====
|
|
+
|
|
* Calls the {JaegerName} Operator to create {JaegerShortName} components based on configuration in either the SMCP or the Jaeger custom resource.
|
|
+
|
|
[NOTE]
|
|
====
|
|
You view the Jaeger components under the {JaegerName} Operator and the Elasticsearch components under the Red Hat Elasticsearch Operator, not the {SMProductShortName} Operator.
|
|
====
|
|
+
|
|
.From the {product-title} console
|
|
|
|
You can verify the {SMProductShortName} control plane installation in the {product-title} web console.
|
|
|
|
. Navigate to *Ecosystem* -> *Installed Operators*.
|
|
. Select the `istio-system` namespace.
|
|
. Select the {SMProductName} Operator.
|
|
.. Click the *Istio Service Mesh Control Plane* tab.
|
|
.. Click the name of your control plane, for example `basic`.
|
|
.. To view the resources created by the deployment, click the *Resources* tab. You can use the filter to narrow your view, for example, to check that all the *Pods* have a status of `running`.
|
|
.. If the SMCP status indicates any problems, check the `status:` output in the YAML file for more information.
|
|
|
|
. Navigate back to *Ecosystem* -> *Installed Operators*.
|
|
. Select the OpenShift Elasticsearch Operator.
|
|
.. Click the *Elasticsearch* tab.
|
|
.. Click the name of the deployment, for example `elasticsearch`.
|
|
.. To view the resources created by the deployment, click the *Resources* tab. .
|
|
.. If the `Status` column any problems, check the `status:` output on the *YAML* tab for more information.
|
|
|
|
. Navigate back to *Ecosystem* -> *Installed Operators*.
|
|
. Select the {JaegerName} Operator.
|
|
.. Click the *Jaeger* tab.
|
|
.. Click the name of your deployment, for example `jaeger`.
|
|
.. To view the resources created by the deployment, click the *Resources* tab.
|
|
.. If the `Status` column indicates any problems, check the `status:` output on the *YAML* tab for more information.
|
|
|
|
. Navigate to *Ecosystem* -> *Installed Operators*.
|
|
. Select the Kiali Operator.
|
|
.. Click the *Istio Service Mesh Control Plane* tab.
|
|
.. Click the name of your deployment, for example `kiali`.
|
|
.. To view the resources created by the deployment, click the *Resources* tab.
|
|
.. If the `Status` column any problems, check the `status:` output on the *YAML* tab for more information.
|
|
|
|
.From the command line
|
|
|
|
. Run the following command to see if the {SMProductShortName} control plane pods are available and running, where `istio-system` is the namespace where you installed the SMCP.
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc get pods -n istio-system
|
|
----
|
|
+
|
|
.Example output
|
|
[source,terminal]
|
|
----
|
|
NAME READY STATUS RESTARTS AGE
|
|
grafana-6776785cfc-6fz7t 2/2 Running 0 102s
|
|
istio-egressgateway-5f49dd99-l9ppq 1/1 Running 0 103s
|
|
istio-ingressgateway-6dc885c48-jjd8r 1/1 Running 0 103s
|
|
istiod-basic-6c9cc55998-wg4zq 1/1 Running 0 2m14s
|
|
jaeger-6865d5d8bf-zrfss 2/2 Running 0 100s
|
|
kiali-579799fbb7-8mwc8 1/1 Running 0 46s
|
|
prometheus-5c579dfb-6qhjk 2/2 Running 0 115s
|
|
----
|
|
+
|
|
. Check the status of the {SMProductShortName} control plane deployment by using the following command. Replace `istio-system` with the namespace where you deployed the SMCP.
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc get smcp -n istio-system
|
|
----
|
|
+
|
|
The installation has finished successfully when the STATUS column is `ComponentsReady`.
|
|
+
|
|
.Example output
|
|
[source,terminal]
|
|
----
|
|
NAME READY STATUS PROFILES VERSION AGE
|
|
basic 10/10 ComponentsReady ["default"] 2.1.3 4m2s
|
|
----
|
|
|
|
+
|
|
If you have modified and redeployed your {SMProductShortName} control plane, the status should read `UpdateSuccessful`.
|
|
+
|
|
.Example output
|
|
[source,terminal]
|
|
----
|
|
NAME READY STATUS TEMPLATE VERSION AGE
|
|
basic-install 10/10 UpdateSuccessful default v1.1 3d16h
|
|
----
|
|
+
|
|
. If the SMCP status indicates anything other than `ComponentsReady` check the `status:` output in the SCMP resource for more information.
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc describe smcp <smcp-name> -n <controlplane-namespace>
|
|
----
|
|
+
|
|
.Example output
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc describe smcp basic -n istio-system
|
|
----
|
|
+
|
|
. Check the status of the Jaeger deployment with the following command, where `istio-system` is the namespace where you deployed the SMCP.
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc get jaeger -n istio-system
|
|
----
|
|
+
|
|
.Example output
|
|
[source,terminal]
|
|
----
|
|
NAME STATUS VERSION STRATEGY STORAGE AGE
|
|
jaeger Running 1.30.0 allinone memory 15m
|
|
----
|
|
+
|
|
. Check the status of the Kiali deployment with the following command, where `istio-system` is the namespace where you deployed the SMCP.
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc get kiali -n istio-system
|
|
----
|
|
+
|
|
.Example output
|
|
[source,terminal]
|
|
----
|
|
NAME AGE
|
|
kiali 15m
|
|
----
|