---
title: Kubernetes cluster creation
description: This page describes the legacy CDM implementation, which will be deprecated in an upcoming release. We strongly recommend that you transition to the current CDM implementation as soon as possible.
component: forgeops
version: 7.2
page_id: forgeops::legacy/cdm/gke/setup/cluster
canonical_url: https://docs.pingidentity.com/forgeops/7.2/legacy/cdm/gke/setup/cluster.html
section_ids:
  next_step: Next step
---

# Kubernetes cluster creation

|   |                                                                                                                                                                                                                                       |
| - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | This page describes the legacy CDM implementation, which will be deprecated in an upcoming release. We strongly recommend that you transition to [the current CDM implementation](../../../../cdm/overview.html) as soon as possible. |

ForgeRock provides shell scripts based on the Google Cloud SDK to use for GKE cluster creation. Use them when you deploy the CDM. After you've finished deploying the CDM, you can use the CDM as a sandbox to explore a different infrastructure-as-code solution, if you like.

When you [Create a Project Plan](../../../../start/start-here.html#planning), you'll need to identify your organization's preferred infrastructure-as-code solution, and create your own cluster creation automation scripts, if necessary.

Here are the steps the Cloud Deployment Team followed to create a Kubernetes cluster on GKE:

1. Create the cluster:

   1. Change to the directory that contains the cluster creation script:

      ```
      $ cd /path/to/forgeops/cluster/gke
      ```

   2. Source the script that contains the configuration for your cluster size. For example:

      ```
      $ source ./small.sh
      ```

   3. Run the cluster creation script\[[1](#_footnotedef_1 "View footnote.")]:

      ```
      $ ./cluster-up.sh
      ```

      If you're prompted to install Google Cloud SDK beta components, enter **Y** to install them.

      The script creates:

      * The cluster

      * The `ds-pool` node pool (for large clusters only)

      * The `fast` storage class

      * The `prod` namespace

      * The `cluster-admin-binding` cluster role binding

   4. To verify that the script created the cluster, log in to the Google Cloud console. Select the Kubernetes Engine option. You should see the new cluster in the list of Kubernetes clusters.

   5. Run the kubectx command.

      The output should contain your newly created cluster and any existing clusters.

      The current context should be set to the context for your new cluster.

2. Set context to the `prod` namespace:

   ```
   $ kubens prod
   ```

3. Check the status of the pods in your cluster until all the pods are ready:

   1. List all the pods in the cluster:

      ```
      $ kubectl get pods --all-namespaces
      NAMESPACE     NAME                                             READY   STATUS    RESTARTS   AGE
      kube-system   event-exporter-gke-5479fd58c8-6gbrj              2/2     Running   0          9m27s
      kube-system   fluentbit-gke-bzztq                              2/2     Running   0          9m10s
      kube-system   fluentbit-gke-fxtzt                              2/2     Running   0          9m11s
      kube-system   fluentbit-gke-vqnjw                              2/2     Running   0          9m9s
      kube-system   gke-metadata-server-7fb5k                        1/1     Running   0          9m9s
      kube-system   gke-metadata-server-h6crf                        1/1     Running   0          9m9s
      kube-system   gke-metadata-server-xq88n                        1/1     Running   0          9m9s
      . . .
      ```

   2. Review the output. Deployment is complete when:

      * The `READY` column indicates all running containers are available. The entry in the `READY` column represents \[total number of containers/number of available containers].

      * All entries in the `STATUS` column indicate `Running` or `Completed`.

   3. If necessary, continue to query your cluster's status until all the pods are ready.

## Next step

* [icon: check-square-o, set=fa][Install third-party software](sw.html)

* [icon: check-square-o, set=fa][Set up a Google Cloud project](project.html)

* [icon: check-square-o, set=fa][Get the forgeops repository](forgeops.html)

* [icon: check-square-o, set=fa][Create a Kubernetes cluster](#)

* [icon: square-o, set=fa]*[Install the Secret Agent operator](secret-agent.html)*

* [icon: square-o, set=fa][Deploy the Ingress-NGINX controller](nginx.html)

* [icon: square-o, set=fa][Deploy certificate manager](cert-manager.html)

* [icon: square-o, set=fa][Deploy Prometheus, Grafana, and Alertmanager](prometheus.html)

* [icon: square-o, set=fa][Prepare to push Docker images](push.html)

***

[1](#_footnoteref_1). The cluster creation script adds a set of required labels to clusters created by ForgeRock employees. The first time you run the script, it prompts you to specify whether you're a ForgeRock employee or not, so that it can add these labels if appropriate. You should not receive this prompt during subsequent executions of the script.