A managed Kubernetes cluster with a node group, an RBAC user role, and a cluster user whose kubeconfig is written to disk. This assumes the Networking example's resources (kvindo_vpc_subnet.demo) are in the same Terraform configuration.

spec.version must be a full X.Y.Z — provisioning downloads release/vX.Y.Z artifacts, so a bare 1.31 never reconciles. Terraform wires the subnet id into control_plane_locations through its own resource graph, so unlike the CLI example there is no id lookup to do by hand.

The apply blocks until the control plane is up, which takes tens of minutes. Scale the pool by raising desired_node_count and re-applying; status.kubeconfig is sensitive, so it is written with local_sensitive_file rather than an output you would then have to mark sensitive.

Related pages

Resource docs

• Kubernetes Cluster resource docs
• Node Group resource docs
• User Role resource docs
• Cluster User resource docs
• VPC Subnet resource docs

More in this section

• Networking
• VMs
• VPN
• Load Balancing
• S3
• Examples

Reference

• Kvindo provider on the Terraform Registry