---
title: "The GKE platform architect role"
chapter: "00"
---

# The GKE platform architect role

Google Kubernetes Engine (GKE) is Google's managed Kubernetes service. A GKE
architect decides how teams safely run containers at scale.

## Explain it like I am five

Imagine an application is a toy made from many small boxes. A **container** is
one box with everything a program needs. **Kubernetes** is the organizer that
puts boxes on computers, replaces broken boxes, and makes more when people need
them. **GKE** is Kubernetes where Google operates much of the organizer.

The architect decides which playground to use, who may enter, how boxes talk,
what happens when a computer breaks, how updates stay safe, and how much it all
costs.

## The job loop

1. Discover outcomes, users, data, scale, recovery, security, and team skills.
2. Decide whether Kubernetes is actually needed.
3. Choose Autopilot or Standard and define cluster/project boundaries.
4. Design identity, network, workload, data, delivery, and operations.
5. Make trade-offs visible to developers, security, finance, and leadership.
6. Prove the design with tests, SLOs, game days, cost data, and recovery drills.

## What strong evidence looks like

- A one-page platform and workload context diagram.
- A cluster-mode decision with rejected alternatives.
- Namespace, IAM, RBAC, and Workload Identity design.
- Network and traffic flow with default-deny policy.
- Resource requests, autoscaling, disruption, and topology policy.
- Supply-chain controls from source to signed image to running Pod.
- SLOs, dashboards, alerts, runbooks, and an upgrade plan.
- RTO/RPO, Backup for GKE restore test, and regional failure plan.
- Cost per request or tenant, not only a monthly invoice.

## The key principle

Kubernetes gives a common API for containers; it does not make an application
secure, reliable, or inexpensive automatically. GKE removes some platform work,
especially in Autopilot, but workload design remains your responsibility.