GCP Cluster Creation Customization Choices

Below are a some methods to customize your cluster during creation. If none of these choices apply, skip this page and proceed to:

GCP Install in a Non-air-gapped Environment

Section Topics

When creating clusters, many options are available such as those listed in this section of the documentation. Familiarize yourself with the flags required to apply these customizations during cluster creation.

GCP Customizing CAPI Clusters — Familiarize yourself with Cluster API before editing the cluster objects because edits can prevent the cluster from deploying successfully.

GCP Registry Mirrors — Configure your cluster to use an existing local registry when attempting to pull images by adding the flag(s) to the dkp create cluster command to pull images from your local registry.

GCP Load the Registry — Because air-gapped environments do not have direct access to the Internet, you must download, extract and load several required images to your local container registry, before installing DKP. If desired, environments that are non-air-gapped can also perform the follow steps to use a local registry for speed and security reasons.

GCP HTTP Proxy — When creating a DKP cluster in environments that use an HTTP/HTTPS proxy, you must provide proxy details. The proxy values are strings that list a set of proxy servers, URLs, or wildcard addresses that is specific to your environment.

GCP Output Directory YAML — You can create individual files with different smaller manifests for ease in editing using the --output-directory flag used with --output=json|yaml. You create the directory of where to output resources to files.

Next Step:

After you make decisions about customization choices, proceed to GCP environment instructions:

GCP Install in a Non-air-gapped Environment