Managed Kubernetes runs the control plane of upstream Kubernetes clusters for you, as one machine or three across zones, with etcd backups and upgrades one minor at a time. Your nodes are compute instances in your network, and kubectl signs in with your {{product}} identity through access entries.
Managed Kubernetes runs the control plane of upstream Kubernetes clusters for you; your nodes are compute instances in your network, and kubectl signs in with your {{product}} identity.
Create a dev cluster with two nodes, run kubectl against it, and delete it again.
What a cluster and a node group are, the two control-plane tiers, zones, the network ranges and the statuses you see.
Create a Kubernetes cluster with a dev or standard control plane, in a network you choose, optionally with a first node group.
Add a cluster to your kubeconfig so kubectl signs in with your {{product}} identity, with no secret stored.
Add a set of compute instances of one server type that join the cluster as nodes, with labels, taints, zones and an optional IAM role for image pulls.
Give an IAM user, group or role an access entry on a cluster with an access policy, change it, or remove it.
Who may do what (IAM), what is recorded, how secrets are encrypted, and who can reach a cluster.
Follow a cluster through its Activity, its control-plane logs, its measured API availability and the metrics you can set alarms on.
What {{product}} runs in and for a cluster, how the control plane and nodes are watched and repaired, and which firewalls surround them.
User Guide
33 pages: concepts, tasks, security, quotas, troubleshooting.
API Reference
44 operations, with their parameters and IAM actions.
CLI Command Reference
44 commands, one per API operation, with their arguments and flags.
Terraform resources
7 resources and data sources of the provider.
Document history
What changed in these docs.