The Terraform Kubernetes provider lets you manage Kubernetes objects (namespaces, deployments, services, config maps, secrets, etc.) by translating Terraform configuration into Kubernetes API calls.
That said, it’s not always the best default for app delivery — many teams prefer Helm/Kustomize/GitOps for in-cluster resources and keep Terraform focused on provisioning the underlying infrastructure. The Kubernetes provider tends to fit best when you want one Terraform-driven workflow across clusters/environments (including multi-cloud) or when platform teams need a consistent IaC interface.
In the full guide, we cover:
- What the provider is and what it can manage in-cluster
- How to configure authentication (kubeconfig/context vs direct host/token/certs)
- Practical examples and best practices (plus when to choose Helm instead)
➡️ Read the full article on our blog:
https://spacelift.io/blog/terraform-kubernetes-provider
Top comments (0)