Skip to content

Releases: appvia/terranetes-controller

terraform-controller-v0.2.8

10 Jun 19:59
094c92f
Compare
Choose a tag to compare

Controller used to provision a terraform workflow within kubernetes

terraform-controller-v0.2.7

10 Jun 10:34
4d1bf32
Compare
Choose a tag to compare

Controller used to provision a terraform workflow within kubernetes

Release v0.2.1

09 Jun 19:45
Compare
Choose a tag to compare

Bug Fixes

  • Fixing a bug in the parsing of the infracost report which was introduced in v0.1.6 release by #96. We were expecting a float64 when actually it's a string

What's Changed

Full Changelog: v0.2.0...v0.2.1

v0.2.0

09 Jun 16:37
e0ca661
Compare
Choose a tag to compare

Features

  • Provider Scope moved to Cluster has been moved to teh cluster scope and away from a namespace resource. #116
  • Drift Detection provides the ability to automatically detect configurations which have drifted from the expected state #131
  • Adding Terraform Version to Status is not exporsed on the terraform state #131
  • Overall Configuration State now provides a synchronization overview of the configuration.

Bug Fixes

Migration

This release introduces a breaking changes; namely the Providers CRD has been moved to a cluster scoped resource. You can use the following to migration any current providers.

# scope the deployment down
$ kubectl -n terraform-system scale deployment terraform-controller --replicas=0
# delete the old provider
$ kubectl -n terraform-system get provider <NAME> -o yaml > saved.1
# Deploy the v0.1.7 version, just change the replicas to 0
$ vim <VALUE_FILE> # change the top replicaCount -> replicaCount: 0
# Perform the upgrade - no changes to the configurations are required. The namespace field in the spec.providerRef is simply ignored.
$ helm upgrade -n terraform-system terraform-controller appvia/terraform-controller --values <VALUE_FILE>
# Apply the providers again
$ kubectl apply -f saved.1
# Change the replicaCount back to 1 and rerun the helm upgrade

What's Changed

Full Changelog: v0.1.6...v0.2.0

terraform-controller-v0.2.6

09 Jun 19:38
Compare
Choose a tag to compare

Controller used to provision a terraform workflow within kubernetes

terraform-controller-v0.2.5

09 Jun 16:38
d357945
Compare
Choose a tag to compare

Controller used to provision a terraform workflow within kubernetes

terraform-controller-v0.2.4

09 Jun 15:53
Compare
Choose a tag to compare

Controller used to provision a terraform workflow within kubernetes

Release v0.1.6

06 Jun 08:07
8a21e50
Compare
Choose a tag to compare

New Features

  • [FEATURE] - Record Configuration Cost Metrics - adds the predicted costs of the configuration as exposed prometheus metrics. By @gambol99 in #96
  • [FEATURE] - Adding the UID Labels - adding the UIDs on the labels for resources to make pinpointing the source configuration easier. By @gambol99 in #100
  • [FEATURE] - Adding Value From fields - The current implementation only allows for variables to come from the spec. In most cases this is fine, but if we take a database password supplied to an RDS module, it's not. These should be kept kubernetes secrets and sources into the terraform module. By @gambol99 in #103

Bug Fixes

What's Changed

New Contributors

Full Changelog: v0.1.5...v0.1.6

terraform-controller-v0.2.3

06 Jun 08:25
c0eea43
Compare
Choose a tag to compare

Controller used to provision a terraform workflow within kubernetes

terraform-controller-v0.2.1

26 May 10:51
Compare
Choose a tag to compare

Controller used to provision a terraform workflow within kubernetes