Skip to main content
Version: 1.47

Google Kubernetes Engine (GKE)

This guide will walk you through the process of installing Okteto in Google Kubernetes Engine (GKE).

Installation Requirements​

Install these CLIs on your machine:

You also need:

  • An Okteto license
  • A domain where you can create wildcard DNS records
  • A Kubernetes cluster

Getting your Okteto License​

You need a license to install Okteto. If you have an Okteto subscription, your license key came with it, and support can send it again if you can't find it. If you don't have a subscription yet, sign up for the free tier: you get a one-year license for up to 5 users and 500 environments per month, and you don't need a credit card.

A Domain and the ability to create wildcard DNS records for it​

You need enough access to a subdomain, such as dev.example.com, to add a wildcard DNS record to it. By default, Okteto exposes the endpoints of your application environments on that subdomain.

This guide uses Google Cloud DNS for the DNS records, but any DNS service works.

Deploy a Kubernetes cluster​

To create the cluster, follow Google's GKE cluster creation guide.

Okteto supports Kubernetes versions 1.33 through 1.35. To get started, we recommend a Kubernetes cluster with this configuration:

  • Kubernetes v1.35
  • A pool with at least 3 n2-standard-4 nodes
  • 250 GB per disk

Installing Okteto​

note

Argo CD installs the same Helm chart declaratively. See Configure Argo CD for the Application manifest, sync policy, and the ignoreDifferences Okteto requires. It replaces Add the Okteto Helm repository and Installing the Okteto Helm chart. Every other step on this page still applies, including the DNS record and the sign-in.

You install Okteto with its Helm chart.

Add the Okteto Helm repository​

Add the Okteto Helm repository:

helm repo add okteto https://charts.okteto.com
helm repo update

Create the Helm configuration file​

Create a config.yaml file with these settings, replacing license and subdomain with your own values:

config.yaml
license: "REPLACE ME WITH YOUR OKTETO LICENSE"
subdomain: "REPLACE ME WITH YOUR OKTETO DOMAIN"

registry:
storage:
filesystem:
persistence:
enabled: true
ARM Node Groups

GKE applies taints to ARM nodes automatically. If your GKE cluster uses ARM-based node groups, add these tolerations to your config.yaml:

globals:
tolerations:
okteto:
- key: "kubernetes.io/arch"
operator: "Equal"
value: "arm64"
effect: "NoSchedule"
dev:
- key: "kubernetes.io/arch"
operator: "Equal"
value: "arm64"
effect: "NoSchedule"
ingress-nginx:
controller:
tolerations:
- key: "kubernetes.io/arch"
operator: "Equal"
value: "arm64"
effect: "NoSchedule"
okteto-nginx:
controller:
tolerations:
- key: "kubernetes.io/arch"
operator: "Equal"
value: "arm64"
effect: "NoSchedule"
reloader:
reloader:
deployment:
tolerations:
- key: "kubernetes.io/arch"
operator: "Equal"
value: "arm64"
effect: "NoSchedule"

The ARM Support guide covers the recommended cluster configuration, the supported instance types (Tau T2A), and the known limitations.

This is the minimum configuration. The Helm configuration lists every setting.

Installing the Okteto Helm chart​

Install the Okteto Helm chart:

helm upgrade --install okteto okteto/okteto -f config.yaml --namespace=okteto --create-namespace --version=1.47.0

After a few seconds, Helm creates all the resources. The output looks like this:

Release "okteto" has been installed. Happy Helming!
NAME: okteto
LAST DEPLOYED: Thu Mar 26 18:07:55 2020
NAMESPACE: okteto
STATUS: deployed

Retrieve the Ingress Controller IP address​

Use kubectl to get the address that GKE allocated to the NGINX ingress controller that Okteto installs:

kubectl get service -l=app.kubernetes.io/name=ingress-nginx,app.kubernetes.io/component=controller --namespace=okteto

The output looks like this:

NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
okteto-ingress-nginx-controller LoadBalancer 10.0.7.73 34.68.230.234 80:30795/TCP,443:32481/TCP,1234:30885/TCP 5m

Add the EXTERNAL-IP address to the DNS of your domain. In Google Cloud DNS, create an A record with the name *. We suggest a TTL of 1 minute.

Sign in to your Okteto instance​

warning

The default installation isn't meant for production. Once you finish your evaluation, and before you give your team access to your Okteto instance, configure a wildcard certificate and Okteto Registry storage with Google Cloud Storage.

Once the installation finishes, your Okteto instance is available at https://okteto.SUBDOMAIN. Okteto creates your account the first time you log in, and the first user to log in gets the Admin role.

Optional: Configure access to your Google Artifact Registry​

You can give Okteto access to your Google Artifact Registry. Your Dockerfiles and your deployments can then use its private images without pull secrets.

Deploy your first app​

With your Okteto instance running, install the Okteto CLI and configure it with the URL of your instance, https://okteto.SUBDOMAIN. Then deploy your first app.