Releases: gardener/terraformer
0.9.0
[terraformer]
Most notable changes
- [USER] An issue with the Alibaba provider plugin has been resolved.
Docker Image
terraformer: eu.gcr.io/gardener-project/gardener/terraformer:0.9.0
0.8.0
Most notable changes:
- The state ConfigMap update is now put within an exponential retry loop. Before this change, the Terraformer only tried exactly once to write its state into the ConfigMap. However, when the API server was not available/responsive at this point in time the Terraformer aborted (and only wrote the ConfigMap to stdout). With this change it should be more resilient against unresponsive API servers. The environment variables
MAX_TIME_SEC
andMAX_BACKOFF_SEC
may be used for configuration the backoff settings.
Docker Image
terraformer: eu.gcr.io/gardener-project/gardener/terraformer:0.8.0
0.7.0
No functional changes; release created due to changes in the CI system.
Docker Image
terraformer: eu.gcr.io/gardener-project/gardener/terraformer:0.7.0
0.6.0
0.5.0
Most notable changes
- Incorporated the
null
Terraform provider.
Docker image: eu.gcr.io/gardener-project/gardener/terraformer:0.5.0
0.4.0
Most notable changes
- Updated Terraform version to
0.11.6
.
Docker image: eu.gcr.io/gardener-project/gardener/terraformer:0.4.0
0.3.0
Most notable changes
- Updated Terraform version to
0.11.5
. - Do not try to update the state config map when no state file was produced by Terraform.
Docker image: eu.gcr.io/gardener-project/gardener/terraformer:0.3.0
0.2.0
Most notable changes
- The input terraform state is copied into another (temporary) directory because it is mounted from a configmap into the pod (read-only) and files cannot be changed. However, Terraform will try to change the directory when running.
Docker image: eu.gcr.io/gardener-project/gardener/terraformer:0.2.0
0.1.0
Initial release
The Terraformer is a tool that can execute Terraform configuration and is designed to run as a pod inside a Kubernetes cluster. The main.tf
, variables.tf
, terraform.tfvars
and terraform.tfstate
files are expected to be stored as configmaps/secrets and mounted into the pods. The Terraformer is able to run terraform validate|plan|apply|destroy
and will update the state configmap itself by using the mounted Kubernetes service account.
Usually, one will run terraform validate|plan
within a single pod and terraform apply|destroy
as a job in order to establish retry logic.
Docker image: eu.gcr.io/gardener-project/gardener/terraformer:0.1.0