Terraform Provider Kustomize
This provider aims to solve 3 common issues of applying a kustomization using kubectl by integrating Kustomize and Terraform.
- Lack of feedback what changes will be applied.
- Resources from a previous apply not in the current apply are not purged.
- Immutable changes like e.g. changing a deployment's selector cause the apply to fail mid way.
To solve this the provider uses the Terraform state to show changes to each resource individually during plan as well as track resources in need of purging.
It also uses server side dry runs to validate changes to the desired state and translate this into a Terraform plan that will show if a resource will be updated in-place or requires a delete and recreate to apply the changes.
As such it can be useful both to replace kustomize/kubectl integrated into a Terraform configuration as a provisioner as well as standalone kubectl diff/apply
steps in CI/CD.
Requirements
Usage
data "kustomization" "example" {
# path to kustomization directory
path = "test_kustomizations/basic/initial"
}
resource "kustomization_resource" "example" {
for_each = data.kustomization.example.ids
manifest = data.kustomization.example.manifests[each.value]
}
Configuring the provider
provider "kustomization" {
# optional path to kubeconfig file
# falls back to KUBECONFIG or KUBE_CONFIG env var
# or finally '~/.kube/config'
kubeconfig_path = "/path/to/kubeconfig/file"
# optional raw kubeconfig string
# overwrites kubeconfig_path
kubeconfig_raw = data.template_file.kubeconfig.rendered
# optional context to use in kubeconfig with multiple contexts
# if unspecified, the default (current) context is used
context = "my-context"
}
State import for kustomization_resource
To import existing Kubernetes resources into the Terraform state for above usage example, use a command like below and replace apps_v1_Deployment|test-basic|test
accordingly. Please note the single quotes required for most shells.
terraform import 'kustomization_resource.test["apps_v1_Deployment|test-basic|test"]' 'apps_v1_Deployment|test-basic|test'
Building and Developing the Provider
To work on the provider, you need go installed on your machine (version 1.13.x tested). The provider uses go mod to manage its dependencies, so GOPATH is not required.
To compile the provider, run go build
as shown below. This will build the provider and put the provider binary in the terraform.d/plugins/linux_amd64/
directory. The provider has not been tested yet on other platforms.
$ go build -o terraform.d/plugins/linux_amd64/terraform-provider-kustomization
In order to test the provider, you can simply run the acceptance tests using go test
. You can set the KUBECONFIG
environment variable to point the tests to a specific cluster or set the context of your current config accordingly. The tests create namespaces on the current context. Kind or Minikube clusters work well for testing.
$ TF_ACC=1 go test -v ./kustomize