Configure a GKE cluster in Cloud Code for IntelliJ
Stay organized with collections
Save and categorize content based on your preferences.
With Cloud Code, you can create a Kubernetes cluster with
Google Kubernetes Engine (GKE).
Create a GKE cluster and add it to your KubeConfig
Cloud Code opens the Google Cloud console so that you can quickly
create a cluster:
To open the Kubernetes Explorer, click
Kubernetes Explorer or navigate to Tools > Cloud Code >
Kubernetes > View Cluster Explorer.
In the header of the Kubernetes Explorer pane, click
+ Connect to a GKE Cluster.
Choose Create a new GKE Cluster or
Create a new GKE Autopilot cluster. For more information on which mode to
choose, see
Comparing Autopilot and Standard modes.
If prompted, click Open to permit Cloud Code to open the
Google Cloud console.
In Google Cloud console, choose any configuration options that you want
to customize and then click Create.
After the cluster is created, in Cloud Code, in the Kubernetes
explorer, click the Refresh icon.
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.
Work 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 Kubernetes Explorer pane, click
+ Add GKE Cluster.
Click Google Kubernetes Engine.
Click your cluster name. Your cluster is added to the KubeConfig.
Set 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 Current Context.
Run an application on GKE
To run or debug an application on GKE, you'll need to define
the container image repository for your project.
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 From KubeConfig.
Create and add a cluster from another cloud provider
If you're using an on-premises 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.
To submit feedback or report an issue in your IntelliJ IDE, go to
Tools > Cloud Code > Help / About > Submit
feedback or report an issue to report an issue on GitHub.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["\u003cp\u003eCloud Code facilitates the creation of a Kubernetes cluster using Google Kubernetes Engine (GKE) directly from the Google Cloud console.\u003c/p\u003e\n"],["\u003cp\u003eExisting Standard or Autopilot GKE clusters can be connected and managed within Cloud Code, and any cluster can be set as the default context for application deployment.\u003c/p\u003e\n"],["\u003cp\u003eCloud Code allows for the management of cluster connections, including adding, removing, and setting the active cluster within the KubeConfig.\u003c/p\u003e\n"],["\u003cp\u003eUsers can utilize clusters from other providers, such as Azure or AWS, by creating them with the respective provider's tools and then adding them to their KubeConfig.\u003c/p\u003e\n"],["\u003cp\u003eCloud code offers features for advanced cluster management, such as organizing access with kubeconfig files, developing and debugging microservices with Skaffold, and using file sync and hot reloading for rapid development.\u003c/p\u003e\n"]]],[],null,["# Configure a GKE cluster in Cloud Code for IntelliJ\n\nWith Cloud Code, you can create a Kubernetes cluster with\nGoogle Kubernetes Engine (GKE).\n| **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](/docs/ci-cd).\n\nCreate a GKE cluster and add it to your KubeConfig\n--------------------------------------------------\n\nCloud Code opens the Google Cloud console so that you can quickly\ncreate a cluster:\n\n1. To open the Kubernetes Explorer, click\n\n **Kubernetes Explorer** or navigate to **Tools** \\\u003e **Cloud Code** \\\u003e\n **Kubernetes** \\\u003e **View Cluster Explorer**.\n\n2. In the header of the Kubernetes Explorer pane, click\n **+ Connect to a GKE Cluster**.\n\n3. Choose **Create a new GKE Cluster** or\n **Create a new GKE Autopilot cluster** . For more information on which mode to\n choose, see\n [Comparing Autopilot and Standard modes](/kubernetes-engine/docs/concepts/autopilot-overview#comparison).\n\n4. If prompted, click **Open** to permit Cloud Code to open the\n Google Cloud console.\n\n5. In Google Cloud console, choose any configuration options that you want\n to customize and then click **Create**.\n\n6. After the cluster is created, in Cloud Code, in the Kubernetes\n explorer, click the **Refresh** icon.\n\n7. After the name of your new cluster appears in the list, click the cluster\n name. Your new cluster is added to the configuration and set as the default\n context.\n\nWork with an existing GKE cluster\n---------------------------------\n\nIf you have an existing Standard or Autopilot GKE cluster, you\ncan set it as your active cluster and work with it using\nCloud Code.\n\n1. In the header of the Kubernetes Explorer pane, click **+ Add GKE Cluster**.\n2. Click **Google Kubernetes Engine**.\n3. Click your cluster name. Your cluster is added to the KubeConfig.\n\nSet a cluster as the default context\n------------------------------------\n\nThe active cluster is the cluster that your application is deployed to by\ndefault.\n\nIn the Kubernetes Explorer, right-click a cluster and then click\n**Set as Current Context**.\n\nRun an application on GKE\n-------------------------\n\nTo run or debug an application on GKE, you'll need to define\nthe container image repository for your project.\n\nTo learn more, read about\n[storing your container images](/code/docs/intellij/configuring-container-image-settings).\n\n\nRemove a cluster from your KubeConfig\n-------------------------------------\n\nAfter you remove a cluster from your KubeConfig, the cluster is not available\nto deploy to.\n\nIn the Kubernetes Explorer, right-click a cluster and then click\n**Remove From KubeConfig**.\n\nCreate and add a cluster from another cloud provider\n----------------------------------------------------\n\nIf you're using an on-premises cluster or a cluster from another provider such\nas Azure or AWS, use the provider's tools to create the cluster and add it to\nyour KubeConfig.\n\nWhat's next\n-----------\n\n- [Organize your cluster access using kubeconfig files](https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/).\n- Learn how to add, delete or switch between your [kubeconfig files in Cloud Code](/code/docs/intellij/kubeconfigs).\n- [Develop and debug parts of a microservice application](/code/docs/intellij/speed-up-k8s-development#develop_microservices_applications_using_skaffold_configurations) using Skaffold.\n- Use [file sync and hot reloading](/code/docs/intellij/speed-up-k8s-development#enable-skaffold-file-sync-and-hot-reloading) to speed up development.\n- [Debug your application in Cloud Code](/code/docs/intellij/debug).\n\nGet support\n-----------\n\nTo submit feedback or report an issue in your IntelliJ IDE, go to **Tools** \\\u003e **Cloud Code** \\\u003e **Help / About** \\\u003e **Submit\nfeedback or report an issue** to report an issue on [GitHub](https://github.com/GoogleCloudPlatform/cloud-code-intellij/issues)."]]
Kubernetes Explorer or navigate to Tools > Cloud Code >
Kubernetes > View Cluster Explorer.