Skip to content

Latest commit

 

History

History
79 lines (60 loc) · 2.09 KB

gke-autopilot.md

File metadata and controls

79 lines (60 loc) · 2.09 KB
Raw

GKE Autopilot

Docs:

Advantages of GKE Autopilot

GKE Autopilot aims to remove some of the maintenance burden of operating a cluster, in exchange for removing some configuration options and setting sane and secure defaults.

In GKE Autopilot, Nodes are not accessible to cluster users, and usage is billed based on Pod usage, not node availability.

GKE Autopilot also enables "Spot Pods", which are like preemptible VMs, but at the Pod level instead of the Node level. Spot Pods are billed at a 60-91% discount compared to normal Pods.

GKE Autopilot also enables Workload Identity.

Using GKE Autopilot with Tekton

You can create an Autopilot cluster like this: gcloud container clusters create-auto ...; see docs.

After you create your GKE Autopilot cluster, you can install Tekton in the normal manner.

Using Spot Pods

Pods can be scheduled as Spot Pods using a node selector:

nodeSelector:
  cloud.google.com/gke-spot: "true"

You can set this in a TaskRun's podTemplate:

apiVersion: tekton.dev/v1beta1
kind: TaskRun
metadata:
  name: mytaskrun
spec:
  taskRef:
    name: mytask
  podTemplate:
    nodeSelector:
      cloud.google.com/gke-spot: "true"

Or for all TaskRuns in a PipelineRun:

apiVersion: tekton.dev/v1beta1
kind: PipelineRun
metadata:
  name: mypipelinerun
spec:
  pipelineRef:
    name: mypipeline
  podTemplate:
    nodeSelector:
      cloud.google.com/gke-spot: "true"

Or you can make this the default for all TaskRuns in the cluster, by updating config-defaults:

$ kubectl edit configmap config-defaults --namespace tekton-pipelines

apiVersion: v1
kind: ConfigMap
metadata:
  name: config-defaults
  namespace: tekton-pipelines
data:
  default-pod-template: |
    nodeSelector:
      cloud.google.com/gke-spot: "true"