mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
130 lines
7.7 KiB
Plaintext
130 lines
7.7 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * installing/installing_gcp/installing-gcp-user-infra.adoc
|
|
// * installing/installing_gcp/installing-restricted-networks-gcp.adoc
|
|
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="installation-gcp-user-infra-installation_{context}"]
|
|
= Completing a {gcp-short} installation on user-provisioned infrastructure
|
|
|
|
After you start the {product-title} installation on {gcp-first}
|
|
user-provisioned infrastructure, you can monitor the cluster events until the
|
|
cluster is ready.
|
|
|
|
.Prerequisites
|
|
|
|
* Ensure the bootstrap process completed successfully.
|
|
|
|
.Procedure
|
|
|
|
. Complete the cluster installation:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ ./openshift-install --dir <installation_directory> wait-for install-complete <1>
|
|
----
|
|
+
|
|
.Example output
|
|
[source,terminal]
|
|
----
|
|
INFO Waiting up to 30m0s for the cluster to initialize...
|
|
----
|
|
<1> For `<installation_directory>`, specify the path to the directory that you
|
|
stored the installation files in.
|
|
+
|
|
[IMPORTANT]
|
|
====
|
|
* The Ignition config files that the installation program generates contain certificates that expire after 24 hours, which are then renewed at that time. If the cluster is shut down before renewing the certificates and the cluster is later restarted after the 24 hours have elapsed, the cluster automatically recovers the expired certificates. The exception is that you must manually approve the pending `node-bootstrapper` certificate signing requests (CSRs) to recover kubelet certificates. See the documentation for _Recovering from expired control plane certificates_ for more information.
|
|
|
|
* It is recommended that you use Ignition config files within 12 hours after they are generated because the 24-hour certificate rotates from 16 to 22 hours after the cluster is installed. By using the Ignition config files within 12 hours, you can avoid installation failure if the certificate update runs during installation.
|
|
====
|
|
|
|
. Observe the running state of your cluster.
|
|
+
|
|
.. Run the following command to view the current cluster version and status:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc get clusterversion
|
|
----
|
|
+
|
|
.Example output
|
|
[source,terminal]
|
|
----
|
|
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
|
|
version False True 24m Working towards 4.5.4: 99% complete
|
|
----
|
|
+
|
|
.. Run the following command to view the Operators managed on the control plane by
|
|
the Cluster Version Operator (CVO):
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc get clusteroperators
|
|
----
|
|
+
|
|
.Example output
|
|
[source,terminal]
|
|
----
|
|
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE
|
|
authentication 4.5.4 True False False 7m56s
|
|
cloud-credential 4.5.4 True False False 31m
|
|
cluster-autoscaler 4.5.4 True False False 16m
|
|
console 4.5.4 True False False 10m
|
|
csi-snapshot-controller 4.5.4 True False False 16m
|
|
dns 4.5.4 True False False 22m
|
|
etcd 4.5.4 False False False 25s
|
|
image-registry 4.5.4 True False False 16m
|
|
ingress 4.5.4 True False False 16m
|
|
insights 4.5.4 True False False 17m
|
|
kube-apiserver 4.5.4 True False False 19m
|
|
kube-controller-manager 4.5.4 True False False 20m
|
|
kube-scheduler 4.5.4 True False False 20m
|
|
kube-storage-version-migrator 4.5.4 True False False 16m
|
|
machine-api 4.5.4 True False False 22m
|
|
machine-config 4.5.4 True False False 22m
|
|
marketplace 4.5.4 True False False 16m
|
|
monitoring 4.5.4 True False False 10m
|
|
network 4.5.4 True False False 23m
|
|
node-tuning 4.5.4 True False False 23m
|
|
openshift-apiserver 4.5.4 True False False 17m
|
|
openshift-controller-manager 4.5.4 True False False 15m
|
|
openshift-samples 4.5.4 True False False 16m
|
|
operator-lifecycle-manager 4.5.4 True False False 22m
|
|
operator-lifecycle-manager-catalog 4.5.4 True False False 22m
|
|
operator-lifecycle-manager-packageserver 4.5.4 True False False 18m
|
|
service-ca 4.5.4 True False False 23m
|
|
service-catalog-apiserver 4.5.4 True False False 23m
|
|
service-catalog-controller-manager 4.5.4 True False False 23m
|
|
storage 4.5.4 True False False 17m
|
|
----
|
|
+
|
|
.. Run the following command to view your cluster pods:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ oc get pods --all-namespaces
|
|
----
|
|
+
|
|
.Example output
|
|
[source,terminal]
|
|
----
|
|
NAMESPACE NAME READY STATUS RESTARTS AGE
|
|
kube-system etcd-member-ip-10-0-3-111.us-east-2.compute.internal 1/1 Running 0 35m
|
|
kube-system etcd-member-ip-10-0-3-239.us-east-2.compute.internal 1/1 Running 0 37m
|
|
kube-system etcd-member-ip-10-0-3-24.us-east-2.compute.internal 1/1 Running 0 35m
|
|
openshift-apiserver-operator openshift-apiserver-operator-6d6674f4f4-h7t2t 1/1 Running 1 37m
|
|
openshift-apiserver apiserver-fm48r 1/1 Running 0 30m
|
|
openshift-apiserver apiserver-fxkvv 1/1 Running 0 29m
|
|
openshift-apiserver apiserver-q85nm 1/1 Running 0 29m
|
|
...
|
|
openshift-service-ca-operator openshift-service-ca-operator-66ff6dc6cd-9r257 1/1 Running 0 37m
|
|
openshift-service-ca apiservice-cabundle-injector-695b6bcbc-cl5hm 1/1 Running 0 35m
|
|
openshift-service-ca configmap-cabundle-injector-8498544d7-25qn6 1/1 Running 0 35m
|
|
openshift-service-ca service-serving-cert-signer-6445fc9c6-wqdqn 1/1 Running 0 35m
|
|
openshift-service-catalog-apiserver-operator openshift-service-catalog-apiserver-operator-549f44668b-b5q2w 1/1 Running 0 32m
|
|
openshift-service-catalog-controller-manager-operator openshift-service-catalog-controller-manager-operator-b78cr2lnm 1/1 Running 0 31m
|
|
----
|
|
+
|
|
When the current cluster version is `AVAILABLE`, the installation is complete.
|