GCP Install in a Non-air-gapped Environment
This section provides instructions to install DKP in a GCP non-air-gapped environment with custom settings. First you create an Bootstrap Cluster and then move the CAPI resources to the workload cluster and delete the bootstrap cluster.
If not already done, refer to Get Started section of the documentation for:
GCP Specific Prerequisites
Before you begin using Konvoy with GCP, you must:
Verify that your Google Cloud project does not have the Enable OS Login feature enabled.
The Enable OS Login feature is sometimes enabled by default in GCP projects. If the OS login feature is enabled, KIB will not be able to ssh
to the VM instances it creates and will not be able to successfully create an image.
To check if it is enabled, use the commands on this page https://cloud.google.com/compute/docs/metadata/setting-custom-metadata#console_2 to inspect the metadata configured in in your project. If you find the the enable-oslogin
flag set to TRUE, you must remove (or set it to FALSE) to use KIB.
The user creating the Service Accounts needs additional privileges in addition to the Editor role.
To deploy a cluster with a custom image in a region where CAPI images are not provided, you need to use Konvoy Image Builder to create your own image for the region.