After you start the {product-title} installation on Google Cloud Platform (GCP) user-provisioned infrastructure, you can monitor the cluster events until the cluster is ready.
-
Deploy the bootstrap machine for an {product-title} cluster on user-provisioned GCP infrastructure.
-
Install the
ocCLI and log in.
-
Complete the cluster installation:
$ ./openshift-install --dir=<installation_directory> wait-for install-complete (1) INFO Waiting up to 30m0s for the cluster to initialize...
-
For
<installation_directory>, specify the path to the directory that you stored the installation files in.ImportantThe Ignition config files that the installation program generates contain certificates that expire after 24 hours. You must keep the cluster running for 24 hours in a non-degraded state to ensure that the first certificate rotation has finished.
-
-
Observe the running state of your cluster.
-
Run the following command to view the current cluster version and status:
$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version False True 24m Working towards 4.3.0-0: 99% complete
-
Run the following command to view the Operators managed on the control plane by the Cluster Version Operator (CVO):
$ oc get clusteroperators NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE authentication 4.3.0-0 True False False 6m18s cloud-credential 4.3.0-0 True False False 17m cluster-autoscaler 4.3.0-0 True False False 80s console 4.3.0-0 True False False 3m57s dns 4.3.0-0 True False False 22m image-registry 4.3.0-0 True False False 5m4s ingress 4.3.0-0 True False False 4m38s insights 4.3.0-0 True False False 21m kube-apiserver 4.3.0-0 True False False 12m kube-controller-manager 4.3.0-0 True False False 12m kube-scheduler 4.3.0-0 True False False 11m machine-api 4.3.0-0 True False False 18m machine-config 4.3.0-0 True False False 22m marketplace 4.3.0-0 True False False 5m38s monitoring 4.3.0-0 True False False 86s network 4.3.0-0 True False False 14m node-tuning 4.3.0-0 True False False 6m8s openshift-apiserver 4.3.0-0 True False False 6m48s openshift-controller-manager 4.3.0-0 True False False 12m openshift-samples 4.3.0-0 True False False 67s operator-lifecycle-manager 4.3.0-0 True False False 15m operator-lifecycle-manager-catalog 4.3.0-0 True False False 15m operator-lifecycle-manager-packageserver 4.3.0-0 True False False 6m48s service-ca 4.3.0-0 True False False 17m service-catalog-apiserver 4.3.0-0 True False False 6m18s service-catalog-controller-manager 4.3.0-0 True False False 6m19s storage 4.3.0-0 True False False 6m20s
-
Run the following command to view your cluster Pods:
$ oc get pods --all-namespaces 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. -