hashicorp/terraform-provider-kubernetes

Description and use

**Brief Summary**
The *hashicorp/terraform-provider-kubernetes* is an open‑source Terraform provider that lets you declaratively manage Kubernetes resources (including custom resources) alongside your infrastructure code. With over 1.7 k stars, active maintenance, and recent releases, it is production‑ready for teams that want to treat Kubernetes objects as part of their IaC pipeline.

**Value**

• **Unified control plane** – Manage clusters, namespaces, deployments, services, CRDs, and other K8s objects from the same Terraform configuration that provisions cloud resources, eliminating ad‑hoc scripts and reducing drift.
• **Reusable, auditable state** – All changes are stored in Terraform state, giving you version‑controlled, reviewable histories of both infrastructure and application‑level resources.
• **Accelerated prototyping** – Developers can spin up fully‑configured clusters and associated workloads with a single terraform apply, shortening the feedback loop for database‑backed or data‑intensive applications.

**Practical Adoption Path**

1. **Pilot** – Fork the repo or add the provider to your existing Terraform setup, run terraform init and apply a minimal manifest (e.g., a namespace and a ConfigMap) to verify connectivity and RBAC.
2. **Integration testing** – Extend the pilot to cover the critical resources you manage (Deployments, Services, Ingress, CRDs). Use terraform plan in CI to ensure changes are predictable.
3. **Policy enforcement** – Pair the provider with Sentinel or Open Policy Agent to enforce security and naming conventions before promotion to production.
4. **Scale‑out** – Gradually migrate legacy kubectl/Helm scripts to Terraform modules, leveraging the provider’s ability to import existing resources (terraform import).

**Production Readiness**

• **High** – The project shows strong activity (last commit 2026‑05‑14), a large community (≈1.7 k stars, >1 k forks), and is written in Go, the language of Terraform core.
• **Risk considerations** – Perform a final review of the license (MPL‑2.0), run a security scan of the provider binary, and confirm that the maintainers are responsive to issues. Once those checks pass, the provider is suitable for a serious pilot and, subsequently, full production deployment.

Use in a workflow

hashicorp/terraform-provider-kubernetes helps teams persist, query, and move data with less custom plumbing.

• manage persistence
• speed up data access
• prototype database-backed apps

Limitations and review notes

High for an OSS candidate: recent activity, adoption, and ecosystem signals are strong enough for a serious pilot.