Google Distributed Cloud air-gapped provides a managed Kubernetes service with
[Google Kubernetes Engine (GKE) Enterprise edition](https://docs.cloud.google.com/kubernetes-engine/docs/concepts/gke-editions#why),
letting you deploy and run container workloads using industry standard
Kubernetes methodologies. Your GDC Sandbox instance comes with three
clusters created for you:

- An *org infrastructure cluster*, which serves as the control plane for your instance, and
- Two *Kubernetes clusters* for running your container workloads.

For details on Google Distributed Cloud air-gapped clusters, see
[Cluster architecture](https://docs.cloud.google.com/distributed-cloud/hosted/docs/latest/gdch/platform/pa-user/clusters#cluster-architecture).

## The org infrastructure cluster

GDC Sandbox provides you an org infrastructure cluster called
`org-1-admin`. The org infrastructure runs the control plane and data plane
components of the organization. It also hosts the Management API server where
all non-container workloads and services are deployed. For example, you would
use the Management API server to launch and control VMs.

To work with the Management API server on the command line, do the following:

1. Make sure that you have downloaded, configured, and authenticated with
   the `gdcloud` command as described in [Connect](https://docs.cloud.google.com/distributed-cloud/sandbox/latest/gdcloud.md.txt).

2. Set a `KUBECONFIG` environment variable and download a kubeconfig file
   for the Management API server:

   ```bash
   export KUBECONFIG=org-1-admin-kubeconfig
   gdcloud clusters get-credentials org-1-admin
   ```

In a similar way, to work with the `org-infra` cluster, do the following:

1. Set a `KUBECONFIG` environment variable and download a kubeconfig file
   for the Management API server:

   ```bash
   export KUBECONFIG=org-1-infra-kubeconfig
   gdcloud clusters get-credentials org-1-infra
   ```

## Kubernetes clusters

Your GDC Sandbox instance comes with two pre-created Kubernetes clusters,
called `user-vm-1` and `user-vm-2`, in the
`org-1` organization. Use these clusters for container-based workloads.

Distributed Cloud supports "shared" clusters for
running container workloads. For more
background, see
[Kubernetes cluster configurations](https://docs.cloud.google.com/distributed-cloud/hosted/docs/latest/gdch/platform/pa-user/cluster-configs).
The clusters `user-vm-1` and `user-vm-2` are of the "shared" cluster type.
GDC Sandbox does not support the "standard" cluster type. Because
`user-vm-1` and `user-vm-2` are shared multi-tenant clusters, users receive
project- and namespace-scoped permissions within attached project namespaces
(for example, through the **Namespace Admin** role). Cluster-scoped permissions
such as `cluster-admin` and creating `CustomResourceDefinitions` (CRDs),
`ClusterRoles`, `ClusterRoleBindings`, or admission webhooks are not granted to
GDC Sandbox users.

> [!WARNING]
> **Warning:** Don't attempt to create new Kubernetes clusters. GDC Sandbox doesn't support additional clusters.

Before deploying container workloads in a new project, you must attach
`user-vm-1` or `user-vm-2` to the project as described in
[Create your first project](https://docs.cloud.google.com/distributed-cloud/sandbox/latest/create-project.md.txt#attach-clusters).

To work with Kubernetes clusters on the command line, do the following:

1. Make sure that you have downloaded, configured, and authenticated with
   the `gdcloud` command as described in [Connect](https://docs.cloud.google.com/distributed-cloud/sandbox/latest/gdcloud.md.txt).

2. Set a `KUBECONFIG` environment variable and download a kubeconfig file
   for the cluster you want to use, either `user-vm-1` or `user-vm-2`.
   The following example downloads a kubeconfig for `user-vm-1`:

   ```bash
   export KUBECONFIG=user-vm-1-kubeconfig
   gdcloud clusters get-credentials user-vm-1 --zone zone1
   ```