Kubernetes · Google Cloud

Google GKE, built from code and kept healthy.

We set up and run GKE (Google Kubernetes Engine, the managed Kubernetes service from Google Cloud) with Terraform, so your clusters are secure, repeatable, and upgraded on time.

  • 200+ open-source Terraform modules
  • 24x7 support plans
  • Rated 5.0 on Clutch
gke-platform.tfhealthy
Google Cloud logoGoogle GKE
Terraform logoTerraform
Kubernetes logoKubernetes
Helm logoHelm
Prometheus logoPrometheus
Grafana logoGrafana
GitHub Actions logoGitHub Actions
Docker logoDocker

Same playbook, every cloud

Running Kubernetes on another cloud?

The challenge

Google runs the brain. The rest is still your job.

Everything around the cluster

Node pools, who can access what, networking, and add-ons like ingress, DNS and certificates are all still yours to set up.

Clusters drift apart

Changes made by clicking in the Google Cloud console slowly make clusters different from each other, and nobody knows exactly why.

Upgrades get pushed back

A new Kubernetes version arrives several times a year. Upgrades wait, because nobody is sure what will break.

What we set up

Your GKE platform, written as code.

Every part is built with Terraform, so your team can read it, rebuild it, and change it safely.

The cluster as code

Built with our open-source terraform-gcp-gke module, so every environment comes from the same code.

  • Node pools
  • Private nodes
  • Network policy

Access and encryption

Workload Identity lets your apps use Google Cloud without stored keys. Nodes get their own limited service account, and secrets can be encrypted with your own Cloud KMS key.

  • Workload Identity
  • Shielded nodes
  • Cloud KMS

Add-ons from code

The extras every cluster needs, installed with Helm through terraform-google-gke-addons instead of by hand.

  • ingress-nginx
  • ExternalDNS
  • cert-manager
  • External Secrets

Autoscaling that fits demand

Node pools grow and shrink with demand, Spot nodes can carry work that is safe to interrupt, and KEDA scales apps on events like queue length.

Free Kubernetes waste calculator →

Monitoring built in

Prometheus and Grafana installed from code, or Google's managed Prometheus, with dashboards and alerts from day one.

Prometheus & Grafana →

Safe, planned upgrades

Clusters follow a GKE release channel, with maintenance windows and blackout dates you choose. Each new version is tested in dev first.

  • Release channels
  • Maintenance windows
  • Dev first

How we work with you

Four steps, done together with your team.

1

Review

We look at your Google Cloud setup and agree on what good looks like: environments, access, and an upgrade plan.

2

Build

We build dev, staging and production from the same Terraform code.

3

Move

We move your workloads over together with your engineers, one service at a time.

4

Run and upgrade

We test each upgrade in dev before production, and keep monitoring in place.

The result: GKE clusters your team can read, rebuild and upgrade from code, with monitoring and security built in, and no single person holding all the knowledge.

Open Source

Read our GKE code first.

Proof

Google Cloud platforms we've delivered.

Related Reading

Go deeper.

FAQs

Questions, Answered.

What is Google GKE, in simple terms?

GKE (Google Kubernetes Engine) is the Kubernetes service from Google Cloud. Google runs the brain of the cluster for you, and your applications run on servers inside your own Google Cloud project. You still need to set up and look after everything around it.

Is GKE the right choice for us?

It fits well if you already run on Google Cloud, or your product leans on Google's data and AI services, and you have several services that need to scale. For a simple app, Cloud Run can be enough. We will tell you honestly which one fits.

How often does a GKE cluster need upgrades?

Several times a year. Google supports each Kubernetes version for a limited time. We put your clusters on a release channel, set maintenance windows, test upgrades in a development cluster first, and then upgrade production.

Can you take over a GKE cluster someone else built?

Yes. We review how it is set up today, then bring it under Terraform step by step, so nothing has to be rebuilt in one risky move.

Are your GKE modules free to use?

Yes. terraform-gcp-gke and terraform-google-gke-addons are open source on GitHub under the Apache 2.0 license. You can read the code before working with us, and you keep using it after.

Industries

Industries We Commonly Support

Cloud Infrastructure Assessment

See exactly where your cloud stands.

A senior engineer reviews your architecture, cost, security, and reliability, then sends back a prioritized findings report, the fixes that matter most, in order.

  • Architecture & scale
  • Cost & efficiency
  • Security & reliability
Book an Assessment

Complimentary · no obligation · no sales pressure

Work With Us

Running GKE, or moving to it? Let's talk.

Tell us how your clusters are set up today and we'll show you what a GKE setup built from code looks like.

Talk to an Expert