Releases: gardener/terraformer
Releases · gardener/terraformer
v2.1.0
[terraformer]
✨ New Features
- [DEPENDENCY] Terraformer is now available in different provider-specific image variants containing only specific terraform provider plugins, which are much smaller in size than the variant containing all provider plugins. The image variant containing all provider plugins is still available for usage under the same tag. For more information see this README section. (#66, @timebertt)
🏃 Others
- [OPERATOR] The configmaps and secrets used to contain terraform configuration, state and variables are now protected with a finalizer against accidental deletion. (#65, @vpnachev)
- [OPERATOR]
terraform-provider-aws
is now updated to3.18.0
(#63, @ialidzhikov) - [DEVELOPER] All terraformer images can be built via
make docker-images
and specific image variants can be built viamake docker-image PROVIDER={all,aws,gcp,...}
. (#66, @timebertt)
v2.0.0
[terraformer]
Action Required
- [DEVELOPER] Terraformer version
v2
now requires to pass in ConfigMap and Secret names via command line flags instead of environment variables and the base command of the docker image has changed to/terraformer
. Please see the examples for more details. (#58, @timebertt) - [DEVELOPER] If your provider extension is deploying terraformer Pods via gardener's terraformer library, please make sure, that you use at least
gardener/gardener@v1.12.0
and setterraformer.UseV2(true)
in order to deploy a PodSpec, that is compatible with terraformerv2
. (#58, @timebertt)
Most notable changes
- [OPERATOR] Terraformer was rewritten in go and now watches the terraform state file in order to continuously update the state ConfigMap to not lose any relevant infrastructure state. (#58, @timebertt)
- [DEVELOPER] You can now run a small e2e test, that creates some lightweight resource on AWS via terraform, by executing
make test-e2e
. (#51, @timebertt)
Improvements
- [DEVELOPER] You can use
make start-dev-container
to start a docker container which can run terraformer and tests in an isolated environment for development and testing. Alsomake start
will run terraformer commands in such a development container. (#58, @timebertt)
Docker Images
terraformer: eu.gcr.io/gardener-project/gardener/terraformer:v2.0.0
v1.5.0
v2.0.0-rc.0
Docker Images
terraformer: eu.gcr.io/gardener-project/gardener/terraformer:v2.0.0-rc.0
v1.4.0
v1.3.0
[terraformer]
Improvements
- [OPERATOR]
terraform-provider-aws
is now updated to2.68.0
. (#42, @ialidzhikov) - [OPERATOR]
terraform-provider-google
andterraform-provider-google-beta
are now updated to3.27.0
. (#42, @ialidzhikov)
Docker Images
terraformer: eu.gcr.io/gardener-project/gardener/terraformer:v1.3.0
v1.2.0
v1.1.0
v1.0.0
[terraformer]
Action Required
- [OPERATOR] The Terraformer does now lookup the relevant data stored in
ConfigMap
s orSecret
s live from the system instead of relying on mounted volumes. This is a breaking change as the volume mount approach does no longer work, please adapt your manifests according to the examples. The rationale behind it is to not rely on potentially stale kubelet cache while it mounts the volume which may, in rare cases, cause state loss. (#37, @rfranzke)
Improvements
- [OPERATOR]
nsxt
andrandom
providers are now removed from the terraform bundle. (#38, @ialidzhikov) - [OPERATOR]
terraformer
does no longer ignore the termination signals sent to PID 1. It does now send a termination signal to the terraform process itself and waits for its completion. This should prevent rare cases in which theterraformer
was not storing the state of created infrastructure resources. (#36, @ialidzhikov)
Docker Images
terraformer: eu.gcr.io/gardener-project/gardener/terraformer:v1.0.0