Ocean is a managed infrastructure service for Kubernetes that automatically adjusts infrastructure capacity and size to meet the needs of pods, containers, and applications.

In this procedure, you will  join an existing GKE cluster to Ocean using the Spot Console


  1. Connect your GCP project to Spot.
    If you have done this already, go on to the next step. If you don’t have a GCP project, go to the Manage Resources page.
  2. Ensure that billing is enabled for your project:
    Learn how to enable billing.
  3. Ensure that you have enabled the Google Kubernetes Engine API:
    Enable the GKE API.

Get Started

  • In the left menu of the Spot console, click Ocean/Cloud Clusters, and click Create Cluster.

Step 1: General

  1. In the General page, enter a Cluster Name and the Location Type and click the Region where the cluster is running. 
    • Cluster Name is the name of the Ocean entity that will be created.
    • Location Type can be either Zonal or Regional.
  2. Select the GKE cluster to import the configuration from.
  3. Click Next.

Step 2: Compute

  1. Ocean imports the compute configuration from your GKE cluster and displays it in the Compute page. Confirm or edit the configuration if need:
    • Machine Types.
      All types are selected by default to grant Ocean the most freedom of operation possible. Click Customize if an adjustment is required.
    • Resource Limit
      • Max vCPUs
      • Max Memory (GB)
    • Additional Configurations
      • Draining Timeout

  1. Optionally, you can import all GKE node pools into Ocean as launch specifications. (The default node pool will be automatically imported.)
  2. Click Next.

Step 3: Connectivity

  1. Create a Spotinst token or use an existing one.
  2. Install the Spotinst Controller. You can do this using Helm or by running kubectl commands.
  3. Click Test Connectivity to ensure the controller functionality.

  4. Click Next.

Note: For a Private GKE Cluster

  1. For a private GKE cluster, install the Spotinst Kubernetes Controller with the following command:
    kubectl apply -f https://spotinst-public.s3.amazonaws.com/integrations/kubernetes/cluster-controller/spotinst-kubernetes-cluster-controller-gcr.yaml
  2. Ensure that your GKE cluster has NAT for the controller to be able to report information to the Ocean SaaS.
  3. Click Test Connectivity to ensure the controller functionality.

Note: Preserve Original Node Pool

Preserve the original node pool and its name in order to sync upgrades of the node pool. The original node pool can be drained from all nodes as long as it is preserved.

For any change in the original node pool please contact us.

Step 4: Review

Review all the Ocean settings you have configured. Click Create to finish or use the  generated JSON template to create the Ocean cluster using other tooling.

You’re all set! Ocean will now ensure the most cost-effective capacity and sizing possible for your cluster.

What’s Next?

Manually scale down your existing GKE nodes in the node pools you migrated to get Ocean to provision pod-driven optimized infrastructure for your existing workloads. To do this, you can use the following command: 

gcloud container clusters resize <cluster_name> --num-nodes=0 --region=<region/zone> --node-pool <node_pool_name>

To avoid unnecessary down time, the scale down of existing nodes should be gradual. For example, run the above command several times, reducing the value of num-nodes gradually. Use num-nodes=0 only on the last time you run the command.