KUBERNETES

Every cluster, managed from one place.

Every cluster you run (self-managed, EKS, AKS, GKE, OKE) in one console with one permission model. No context switching, no stale kubeconfig on someone’s laptop.

Install itSee the security model
kubectl·Helm·EKS / AKS / GKE / OKE·k3s·kubeadm

SEE IT RUN

Kubernetes in Talos2:43

THE MANUAL WAY

Where cluster management goes wrong.

02:14 · TUESDAY

A pod is crash-looping in a cluster you set up eleven months ago. You are hunting for which of six kubeconfig contexts is the right one before you can even read the logs.

ONBOARDING WEEK 1

A new engineer needs read access to staging. You end up sending them a kubeconfig with cluster-admin because carving out a narrower RBAC role is a half-day of yaml.

AFTER THE INCIDENT

Someone scaled a deployment during the outage. Nobody can say who, when, or what the replica count was before; kubectl leaves no trail you can query.

WHAT TALOS DOES

Things you stop doing by hand.

Cluster inventory

Every cluster, node pool and version in one table, polled from the API server rather than remembered.

Workload browser

Deployments, statefulsets, daemonsets and pods with live status, without a terminal or a kubeconfig on your machine.

Streaming pod logs

Follow logs across replicas in the same log pane as every other Talos job.

Scale and restart

Replica changes and rollout restarts run as tracked jobs. Each records the previous value, so a revert is one click.

Helm releases

Install, upgrade and roll back releases with values diffed against what is currently deployed before you commit.

Node operations

Cordon, drain and uncordon as gated jobs, so draining a production node needs approval from a second person.

talos.internal/kubernetes/prod-eu
Servers
Cloud
Kubernetes
Docker
Databases
Frappe
Pipelines
Monitoring
MLOps
Proxy
DNS & SSL
MCP
Clusters6 clusters · 43 nodes · 2 warnings
prod-eu · EKSHEALTHY
1.29 · 12 nodes · eu-west-1
prod-us · GKEHEALTHY
1.29 · 14 nodes · us-east4
staging · k3sDRAINING
1.30 · 4 nodes · on-prem
edge-ap · AKSSKEW
1.28 · 6 nodes · southeastasia
$ k8s rollout restart deploy/web -n prod
→ 3 replicas affected
⏸ awaiting approval · gated namespace
✓ approved by r.dalca · executing
✓ rollout complete · 18.2s · job #7741

HOW IT RUNS

Every action is a tracked job.

Requestyou, API or schedule
Queueapproval if required
Job runnerbackground worker
ExecutionSSH · Ansible · Terraform · API
Your infrastructurelogs stream back live

WHAT MAKES THIS DIFFERENT

Connect the cloud account. The clusters appear.

Managed clusters are the easiest to lose track of: someone creates an EKS cluster for a project, and eighteen months later nobody remembers it exists. Talos imports them automatically: attach an AWS, Azure, GCP or Oracle account and every cluster in it is discovered, inventoried and permission-mapped without a single kubeconfig being copied.

Credentials are issued per job; no long-lived kubeconfig is written to disk.
New clusters created outside Talos still show up on the next discovery sweep.
Deleted clusters are marked gone rather than silently vanishing from your inventory.
discovery · aws-production
✓
eks/prod-eu-1
bridged · 12 nodes · rbac mapped
READY
✓
eks/data-pipeline
bridged · 5 nodes · rbac mapped
READY
+
eks/ml-sandbox
newly discovered · created 2024-11
NEW
✕
eks/legacy-api
no longer present upstream
GONE

RELATED CAPABILITIES

Cloud

Provision the accounts and networks the clusters live in.

explore →

Deployments

Ship applications onto these clusters through gated pipelines.

explore →

Monitoring

Alerts on node pressure, pod restarts and version skew.

explore →

Point it at one cluster first.

Discovery is read-only. It will tell you what it found before it changes anything.

Install in one commandSee every capability →