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).

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.serviceAgent IAM role.
- Enabled the following APIs at the project level:
  - file.googleapis.com
  - gkehub.googleapis.com
    These APIs and permissions are required for filestore provisioning, CSI driver operations, and certificate management within GKE.

Perform the following steps to configure DNS and network resources:
1. Create a host name in Cloud DNS for the DevOps Loop application.
2. Reserve a global static IPv4 address in the same GCP project.
3. 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 StorageClass for DevOps Loop:
1. Create a custom RWX StorageClass with 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 custom StorageClass is required so filestore volumes are created within your cluster’s VPC. Otherwise, GCP-provided filestore classes attempt provisioning under the default network.
Verify available StorageClasses by running the following command:
```
kubectl get storageclass
```

You have prepared the required Google Cloud Platform (GCP) infrastructure for deploying DevOps Loop on Google Kubernetes Engine (GKE).

You can now proceed with installing DevOps Loop on GKE.