Managing Kubernetes clusters

With Cloud Code, you can create a Kubernetes cluster with Google Kubernetes Engine (GKE) or minikube. You can also work with a local cluster if you're using Docker Desktop.

Note: For developing and testing an app, create and run on a non-production cluster. For changes that will be rolled out to production, use an automated CI/CD workflow.

Creating a GKE cluster and adding it to your KubeConfig

The Kubernetes Explorer opens the Google Cloud Console so that you can quickly create a cluster:

1. To open the Kubernetes Explorer, click Cloud Code - Kubernetes.
2. In the header of the Kubernetes Explorer pane, click + Add a Cluster to the KubeConfig.
3. Choose Google Kubernetes Engine and then click + Create a new GKE Cluster.
4. Choose Standard or Autopilot. For more information, see Comparing Autopilot and Standard modes.
5. If prompted, click Open to permit Cloud Code to open the Cloud Console.
6. In Cloud Console, choose any configuration options that you want to customize and then click Create.
7. After the cluster is created, in VS Code, click Refresh.
8. After the name of your new cluster appears in the list, click the cluster name. Your new cluster is added to the configuration and set as the default context.

Tip: To create a Kubernetes cluster using the Command Palette, launch the Command Palette (click Manage > Command Palette or press Ctrl/Cmd+Shift+P) and then run the Cloud Code: Create GKE cluster command.

Working with an existing GKE cluster

If you have an existing Standard or Autopilot GKE cluster, you can set it as your active cluster and work with it using Cloud Code.

1. In the header of the Kubernetes Explorer pane, click + Add a Cluster to the KubeConfig.
2. Click Google Kubernetes Engine.
3. Click your cluster name. Your cluster is added to the KubeConfig.

Setting a cluster as the default context

The active cluster is the cluster that your application is deployed to by default.

In the Kubernetes Explorer, right-click a cluster and then click Set as Active Cluster.

Removing a cluster from your KubeConfig

After you remove a cluster from your KubeConfig, the cluster is not available to deploy to.

In the Kubernetes Explorer, right-click a cluster and then click Remove Context Under Cluster.

Starting a minikube cluster

Note: Cloud Code automatically installs and manages minikube. If you opted out of dependency management, you'll need to add the minikube binary to your PATH.

1. Click the minikube status bar.

   

2. After the Choose a Minikube (cluster) profile to control option populates, click minikube and then click Start.

Pausing or stopping a minikube cluster

1. Click the minikube status bar.

   

2. After the Choose a Minikube (cluster) profile to control option populates, click minikube and then click Stop or Pause.

Creating and adding a cluster from another cloud provider

If you're using an on-prem cluster or a cluster from another provider such as Azure or AWS, use the provider's tools to create the cluster and add it to your KubeConfig.

Working with local clusters

In addition to minikube, you can also work with Cloud Code if you're using Docker Desktop (for Mac or Windows).

To get Cloud Code working with a local cluster, make sure that your default configuration (for example, ~/.kube/config) contains your local cluster. This cluster must be set as the current context.

For example, if you were using a local cluster, docker-for-desktop, with Docker Desktop, set your preferred cluster by running the following command:

kubectl config use-context docker-for-desktop

Getting Support

To send feedback, report issues on GitHub, or ask a question on Stack Overflow.