Installation on Google Cloud Platform
Setup GCP project
DNS zone
Service Account and permissions
Cluster setup
prepare installer configuration
run installer
Synfection
Post install configuration
Prerequisites
-
GCP project setup according to GCP Project Setup
-
Service Account Key (key.json)
If the project and region names are too long, node provisioning won’t work. See Name length on GCP. |
Purser can be used to check if the preconditons are met. |
Required input
<base domain>
-
The base domain used to make the cluster available.
<cluster name>
-
The name of the cluster. This name will be used as identifier or as part of identifiers. It also will become a subdomain to the base domain.
<service account key>
<region>
-
The GCP region to place the cluster. Default to
europe-west6
Install cluster
-
Obtain the installer and pull secret
-
Copy
<service account key>
to~/.gcp/osServiceAccount.json
-
Create an SSH key for that cluster
ssh-keygen -t rsa -b 4096 -N '' -f ~/.ssh/<cluster name> -C <cluster name>
The key must be within the home directory to be picked up by the installer. -
Create the default installer config
openshift-install create install-config --dir=<cluster name>-config (1)
1 The cluster name from the inputs. Answers- SSH Public Key
-
~/.ssh/<cluster namme>
- Platform
-
gcp
- Project ID
-
Will be extracted from the service account key file.
- Region
-
<region>
- Base Domain
-
<base domain>
- Cluster Name
-
<cluster name>
- Pull Secret
-
Review and tweak installer config
Use your editor of choice to review the created installer config. Make changes where required.
-
Make a copy of the installer config
Once the installer gets executed, the config will be consumed and deleted. If the installer fails and another attempt must be made, a copy of the config is a good thing to have.
cp -r <cluster name>-config <cluster name>
-
Run the installer
openshift-install create cluster --log-level=debug --dir=<cluster name>
Takes roughly 45 minutes to complete. The installer might timeout. This doesn’t necessarily indicate a failed setup. Waiting some more time might be enough.
-
Put the
kubeadmin
credentials into password managerCreate a new password record. Use
kubeadmin
as username and the password from<cluster name>/auth/kubeadmin-password
. Also upload<cluster name>/auth/kubeconfig
as an attachment. -
Gain access to the OpenShift/Kubernetes API
export KUBECONFIG=<cluster name>/auth/kubeconfig
-
Synfection
Synfect the cluster according to wiki.vshn.net/x/ngMBCg.