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.
Creating a GKE cluster and adding it to your KubeConfig
The Kubernetes section opens the Google Cloud console so that you can quickly create a cluster. To access the Kubernetes section and create a cluster, perform the following:
Click
Cloud
Code and then expand the Kubernetes section.Click + Add a Cluster to the KubeConfig.
Select Google Kubernetes Engine and then select Yes to enable container GCP API under your project.
Choose Standard or Autopilot. For more information, see Comparing Autopilot and Standard modes.
If prompted, click Open to permit Cloud Code to open the Cloud console.
In Cloud console, choose any configuration options that you want to customize and then click Create.
After the cluster is created, in VS Code, click
Refresh.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.
- In the header of the expanded Kubernetes section, click + Add a Cluster to the KubeConfig.
- Click Google Kubernetes Engine.
- 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 expanded Kubernetes section, 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 expanded Kubernetes section, right-click a cluster and then click Remove Context Under Cluster.
Starting a minikube cluster
- Launch the Command Palette (click
Manage > Command Palette or press
Ctrl/Cmd+Shift+P) and then run the Cloud Code: Control minikube command. - After the Choose a Minikube cluster (profile) to control option populates, click minikube and then click Start.
Pausing or stopping a minikube cluster
- Launch the Command Palette (click
Manage > Command Palette or press
Ctrl/Cmd+Shift+P) and then run the Cloud Code: Control minikube command. - After the Choose a Minikube cluster (profile) to control option populates, click minikube and then click Stop or Pause.
Opening an interactive terminal to a container
- In the expanded Kubernetes section, expand your minikube cluster, expand Pods, and then expand Containers.
- Right-click a container and then click Get Terminal.
Opening an external IP address
- In the expanded Kubernetes section, expand your minikube cluster and then expand Services.
- Expand External IPs, right-click an IP address, and then click Open Address.
- Click Open.
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 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