A Terraform provider for managing Rancher 2.x Kubernetes management platform resources as infrastructure-as-code.
Terraform Provider for Rancher2 is an open-source Terraform provider that enables infrastructure-as-code management of Rancher 2.x Kubernetes management platform. It allows developers and operators to define Rancher resources like clusters, projects, and users using Terraform configuration files, automating deployment and management workflows.
DevOps engineers, SREs, and platform teams who manage Rancher 2.x deployments and want to automate Kubernetes cluster management using Terraform's infrastructure-as-code approach.
This provider offers a declarative, version-controlled way to manage Rancher resources, reducing manual configuration errors and enabling reproducible environments. Its version alignment with Rancher releases ensures compatibility and reliable integration with existing Rancher deployments.
Terraform Rancher2 provider
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Enables defining Rancher resources like clusters and projects in Terraform HCL, allowing version-controlled, reproducible deployments as highlighted in the README's philosophy.
Provider major versions are aligned with Rancher minor releases (e.g., v13.x for Rancher 2.13.x), ensuring reliability and reducing integration risks, as detailed in the branching strategy.
Supports a wide range of Rancher resources including clusters, projects, namespaces, and users, facilitating full lifecycle management through Terraform's plan-apply workflow.
Follows a structured release process with backporting and alignment to Rancher's lifecycle, ensuring ongoing support and bug fixes for each minor version.
The README explicitly states that unit tests are currently non-functional, limiting automated quality assurance and increasing reliance on costly acceptance tests.
Acceptance tests require AWS credentials and incur real expenses, making thorough validation expensive and prohibitive for resource-constrained teams.
Building from source requires Go installation and specific GOPATH setup, adding overhead for custom modifications or local development, as outlined in the build instructions.