Preparing GCP infrastructure for installing DevOps Loop on GKE
You must set up the required Google Cloud Platform (GCP) infrastructure including DNS, a global static IP address, and RWX Storage, before deploying DevOps Loop on Google Kubernetes Engine (GKE).
Before you begin
You must have completed the following tasks:
-
Ensured that your GCP environment includes the required roles and APIs:
- The service account used for the GKE cluster must have the
roles/file.serviceAgentIAM role. - Enabled the following APIs at the project level:
file.googleapis.comgkehub.googleapis.comThese APIs and permissions are required for filestore provisioning, CSI driver operations, and certificate management within GKE.
- The service account used for the GKE cluster must have the
Procedure
-
Perform the following steps to configure DNS and network resources:
- Create a host name in Cloud DNS for the DevOps Loop application.
- Reserve a global static IPv4 address in the same GCP project.
- Create a DNS A record that maps the domain name to the global static IP address.
For example:- Name:
<host-name> - Type:
A - Value:
<GLOBAL_STATIC_IP>
Note: DNS must resolve and must be visible from the public internet or at least from GCP checkers for GKE-managed certificate provisioning to succeed. -
Perform the following steps to configure
RWX StorageClassfor DevOps Loop:-
Create a custom
RWX StorageClasswith the following requirements:-
Minimum 1 TiB storage
-
Provisioner:
filestore.csi.storage.gke.io -
VPC: must match the VPC network used by your GKE cluster
-
Note: A customStorageClassis required so filestore volumes are created within your cluster’s VPC. Otherwise, GCP-provided filestore classes attempt provisioning under the default network. -
-
Verify available
StorageClassesby running the following command:kubectl get storageclass
