---
title: Setup for shared cloud cluster
description: Before you can deploy the CDK, you must first set up your local environment to communicate with the shared cluster.
component: forgeops
version: 7.4
page_id: forgeops::cdk/cloud/setup/overview
canonical_url: https://docs.pingidentity.com/forgeops/7.4/cdk/cloud/setup/overview.html
keywords: ["CDK", "Google Cloud", "AWS", "Azure"]
section_ids:
  important_information_for_users_running_microsoft_windows: Important information for users running Microsoft Windows
  important_information_for_users_running_macos_on_arm_based_m1_chipsets: Important information for users running macOS on ARM-based (M1) chipsets
  setup_checklists: Setup checklists
  gke_shared_cluster: GKE shared cluster
  eks_shared_cluster: EKS shared cluster
  aks_shared_cluster: AKS shared cluster
---

# Setup for shared cloud cluster

Before you can deploy the CDK, you must first set up your local environment to communicate with the shared cluster.

## Important information for users running Microsoft Windows

ForgeRock supports deploying the CDK and CDM using macOS and Linux. If you have a Windows computer, you'll need to create a Linux VM. We tested using the following configurations:

* Hypervisor: Hyper-V, VMWare Player, or VMWare Workstation

* Guest OS: Current Ubuntu LTS release with 12 GB memory and 60 GB disk space

* Nested virtualization enabled in the Linux VM.

**Perform all the procedures in this documentation within the Linux VM. In this documentation, the local computer refers to the Linux VM for Windows users.**

|   |                                                                                                                                                                                                                                                                                                                                                      |
| - | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|   | The Minikube implementation on Windows Subsystem for Linux (WSL2) has networking issues. As a result, consistent access to the ingress controller or the apps deployed on Minikube is not possible. This issue is tracked [here](https://github.com/kubernetes/minikube/issues/7879). Do not deploy CDK or CDM on WSL2 until this issue is resolved. |

## Important information for users running macOS on ARM-based (M1) chipsets

Running the CDK is currently not supported on macOS systems running an ARM-based chipset, such as the Apple M1 or Apple M1 Max.

Refer to [the Release Notes](../../../rn/limitations.html#platform-limitations) for a workaround.

## Setup checklists

Perform the tasks in the checklist *for your cloud provider only.*

### GKE shared cluster

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

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

* [icon: square-o, set=fa][Get details about the shared GKE cluster](gke/clusterinfo.html)

* [icon: square-o, set=fa][Create a Kubernetes context](gke/context.html)

* [icon: square-o, set=fa][Create a Kubernetes namespace](gke/namespace.html)

* [icon: square-o, set=fa][Set up hostname resolution](gke/hostname.html)

### EKS shared cluster

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

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

* [icon: square-o, set=fa][Get details about the shared EKS cluster](eks/clusterinfo.html)

* [icon: square-o, set=fa][Create a Kubernetes context](eks/context.html)

* [icon: square-o, set=fa][Create a Kubernetes namespace](eks/namespace.html)

* [icon: square-o, set=fa][Set up hostname resolution](eks/hostname.html)

### AKS shared cluster

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

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

* [icon: square-o, set=fa][Get details about the shared AKS cluster](aks/clusterinfo.html)

* [icon: square-o, set=fa][Create a Kubernetes context](aks/context.html)

* [icon: square-o, set=fa][Create a Kubernetes namespace](aks/namespace.html)

* [icon: square-o, set=fa][Set up hostname resolution](aks/hostname.html)

After you've completed these environment setup tasks, you're ready to [deploy the Ping Identity Platform in your namespace on the shared cluster](../../deploy.html).