1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Files
openshift-docs/modules/verifying-cluster-install-oci-agent-based.adoc

115 lines
4.7 KiB
Plaintext
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
// Module included in the following assemblies:
//
// * installing/installing_oci/installing-oci-agent-based-installer.adoc
ifeval::["{context}" == "installing-c3-agent-based-installer"]
:c3:
endif::[]
ifeval::["{context}" == "installing-pca-agent-based-installer"]
:pca:
endif::[]
:_mod-docs-content-type: PROCEDURE
ifdef::c3[]
[id="verifying-cluster-install-oci-agent-based_{context}"]
= Verifying that your Agent-based cluster installation runs on {oci-edge-no-rt}
Verify that your cluster was installed and is running effectively on {oci-edge-no-rt}.
.Prerequisites
* You created all the required {oci-first-no-rt} resources and services. See the "Creating {oci} infrastructure resources and services" section.
* You created `install-config.yaml` and `agent-config.yaml` configuration files. See the "Creating configuration files for installing a cluster on {oci-edge-no-rt}" section.
* You uploaded the agent ISO image to a default Oracle Object Storage bucket, and you created a compute instance on {oci-edge-no-rt}. For more information, see "Running a cluster on {oci-edge-no-rt}".
endif::c3[]
ifdef::pca[]
[id="verifying-cluster-install-oci-agent-based_{context}"]
= Verifying that your Agent-based cluster installation runs on {oci-pca-short}
Verify that your cluster was installed and is running effectively on {oci-pca-short}.
.Prerequisites
* You created all the required {oci-pca} resources and services. See the "Creating {oci-pca-no-rt} infrastructure resources and services" section.
* You created `install-config.yaml` and `agent-config.yaml` configuration files. See the "Creating configuration files for installing a cluster on {oci-pca-short}" section.
* You uploaded the agent ISO image to a default Oracle Object Storage bucket, and you created a compute instance on {oci-pca-short}. For more information, see "Running a cluster on {oci-pca-short}".
endif::pca[]
ifndef::pca,c3[]
[id="verifying-cluster-install-oci-agent-based_{context}"]
= Verifying that your Agent-based cluster installation runs on {oci-distributed-no-rt}
Verify that your cluster was installed and is running effectively on {oci-distributed}.
.Prerequisites
* You created all the required {oci} resources and services. See the "Creating {oci-distributed-no-rt} infrastructure resources and services" section.
* You created `install-config.yaml` and `agent-config.yaml` configuration files. See the "Creating configuration files for installing a cluster on {oci-distributed-no-rt}" section.
* You uploaded the agent ISO image to a default Oracle Object Storage bucket, and you created a compute instance on {oci-distributed-no-rt}. For more information, see "Running a cluster on {oci-distributed-no-rt}".
endif::pca,c3[]
.Procedure
After you deploy the compute instance on a self-managed node in your {product-title} cluster, you can monitor the clusters status by choosing one of the following options:
* From the {product-title} CLI, enter the following command:
+
[source,terminal]
----
$ ./openshift-install agent wait-for install-complete --log-level debug
----
+
Check the status of the `rendezvous` host node that runs the bootstrap node. After the host reboots, the host forms part of the cluster.
+
* Use the `kubeconfig` API to check the status of various {product-title} components. For the `KUBECONFIG` environment variable, set the relative path of the cluster's `kubeconfig` configuration file:
+
[source,terminal]
----
$ export KUBECONFIG=~/auth/kubeconfig
----
+
Check the status of each of the cluster's self-managed nodes. CCM applies a label to each node to designate the node as running in a cluster on {oci}.
+
[source,terminal]
----
$ oc get nodes -A
----
+
.Output example
+
[source,terminal]
----
NAME STATUS ROLES AGE VERSION
main-0.private.agenttest.oraclevcn.com Ready control-plane, master 7m v1.27.4+6eeca63
main-1.private.agenttest.oraclevcn.com Ready control-plane, master 15m v1.27.4+d7fa83f
main-2.private.agenttest.oraclevcn.com Ready control-plane, master 15m v1.27.4+d7fa83f
----
+
Check the status of each of the cluster's Operators, with the CCM Operator status being a good indicator that your cluster is running.
+
[source,terminal]
----
$ oc get co
----
+
.Truncated output example
+
[source,terminal]
----
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
authentication 4.21.0-0 True False False 6m18s
baremetal 4.21.0-0 True False False 2m42s
network 4.21.0-0 True True False 5m58s Progressing: …
----
ifeval::["{context}" == "installing-c3-agent-based-installer"]
:!c3:
endif::[]
ifeval::["{context}" == "installing-pca-agent-based-installer"]
:!pca:
endif::[]