Terraform Enterprise 2.0.1 is available

Terraform HCP Terraform
, ,
1

The Terraform Enterprise team would like to announce the release 2.0.1 is now available.

Some key highlights and important bits from the release notes:

Known Issues

  1. When a Terraform Enterprise node enters a draining state, readiness checks return an HTTP 503 status. In some non‑Kubernetes cloud environments, checks for load balancers may interpret this as an unhealthy node and remove it from service, even though the node is intentionally draining and not accepting new requests. When draining nodes in your Terraform Enterprise installation, consider disabling readiness checks and instead use host-level health signals. For example, you can enable Auto Scaling Group instance checks in AWS, disable auto-repair in AWS, or disable auto-healing policies in GCP. This issue does not affect Terraform Enterprise deployments on Kubernetes or OpenShift.

Bug Fixes

  1. Terraform Stacks runs now complete successfully on Kubernetes and OpenShift deployments. In Terraform Enterprise 2.0.0, Terraform Stacks runs would fail when Terraform Enterprise was deployed on Kubernetes or OpenShift.
  2. When database monitoring was enabled, the database connection would terminate after a restart in some Terraform Enterprise components, mainly the operator admin UI/API. These components now refresh correctly when a DB monitor triggers a restart.
  3. The Terraform Enterprise task worker check now correctly returns a DRAINING status instead of ERROR during a node drain.