Skip to content

v0.9.0

Choose a tag to compare

@anoop2811 anoop2811 released this 16 Nov 02:35
· 27 commits to master since this release
2ea566a

The first final release of the 0.9 line, and a security fix for CVE-2026-111497 (Brotli) and
the eMudhra CA compromise. Since v0.8.0, the 0.9 line also moves to current Go and Kubernetes
libraries and fixes several controller bugs.

Security

The v0.8.0 / v0.9.0-alpha.1 controller image and the images it starts were affected:

  • The controller image was built FROM alpine (unpinned) with git installed, which brings
    brotli-libs (CVE-2026-111497), and its CA store still trusted the compromised eMudhra / emSign
    roots (14 of 14 test chains accepted).
  • The default runner oamdev/docker-terraform:1.1.5 (Alpine 3.13) has both problems; the code's
    fallback runner was even older (1.1.2).
  • gitImage and busyboxImage defaulted to latest.

Fixed in this release:

  • Controller image: runtime alpine:3.24, pinned by digest (3.24.4,
    ca-certificates-bundle 20261020). git and the unused bin/terraform (Terraform v1.0, amd64,
    unused since 2021) are removed: the controller runs no programs itself.
  • Default runner: terraformImage and the code's fallback are now
    oamdev/docker-terraform:1.1.6@sha256:92a21948dfb27dd2e842077adcc769dd85bcf8b1e0785eb0abcf24895858b881:
    the same Terraform (1.1.9) on Alpine 3.24.
  • Init images pinned: gitImage: alpine/git:2.54.0@sha256:6a1fdb96… and
    busyboxImage: busybox:1.38.0@sha256:a46257e0….

Scan result: the controller image has no Brotli finding, and its trust store rejects all 14
eMudhra test chains (amd64 and arm64).

Other changes since v0.8.0

  • Go 1.27.1, Kubernetes client libraries v0.37.1, controller-runtime v0.25.2 (from Go 1.17,
    client-go v0.21.3, controller-runtime v0.9.5).
  • linux/arm64 image fixed: it now contains an arm64 controller (it contained an x86-64 one).
  • Git credentials with current alpine/git: ssh-agent uses a socket under /tmp; with
    OpenSSH 10 it tried $HOME/.ssh/agent, under the read-only Secret mount, so every spec.remote
    clone with gitCredentialsSecretReference failed (Couldn't prepare agent socket).
  • Stale status: a Configuration no longer stays in ProvisioningAndChecking after its apply Job
    succeeds.
  • Kubernetes backend: the Terraform state lock Lease is deleted when the backend is cleaned up.
  • jobNodeSelector works: the chart wrote it unquoted, so the JSON string it documented made
    the Deployment invalid and a map was silently ignored. It now takes a map or a JSON string; a value
    already wrapped in single quotes (the old workaround) keeps working. To remove it later, use
    helm upgrade --reset-then-reuse-values --set jobNodeSelector=null (with --reuse-values, Helm
    keeps the old map; --reset-then-reuse-values needs Helm 3.14 or later).
  • Docs: getting-started.md uses the chart repository that exists
    (https://kubevela.github.io/charts; charts.kubevela.net no longer resolves).
  • CI: e2e on release branches, actions pinned by SHA, the image built on PRs, release candidates
    from release branches.

Upgrade notes

helm repo update kubevela
helm upgrade terraform-controller kubevela/terraform-controller --version 0.9.0 -n <namespace>
  • Without --reuse-values, or set the images yourself: with --reuse-values, Helm keeps the
    previous release's gitImage: alpine/git:latest and busyboxImage: busybox:latest, and the new
    pinned defaults don't apply.

  • Existing Configurations keep their state. They move to the new runner at their next change
    or deletion; the Terraform version is the same, so the state is compatible (tested with
    Configurations created by v0.8.0 on runner 1.1.5, upgraded in one helm upgrade).

  • CRDs: the changes since v0.8.0 are descriptions only (regenerated); nothing to apply.

  • Runner images are linux/amd64 only. Configuration Jobs need amd64 nodes; the controller
    itself now runs natively on arm64. Multi-arch runners come with docker-terraform 1.3.0. To keep
    Jobs on amd64 nodes:

    jobNodeSelector:
      kubernetes.io/arch: amd64
  • Terraform 1.5: set terraformImage=oamdev/docker-terraform:1.2.1@sha256:8054ece3519c4752767583b3d6c4395afeb19d35a96ecc849104cf4aaff67065.

  • If you need to stay on the 0.8 line, v0.8.1 has the same security fixes.

Image

oamdev/terraform-controller:v0.9.0@sha256:3eeb37905f565ddee283f0ebf2ecdb0610d0d97847b8cb9a2aa2f641a826cccd (linux/amd64, linux/arm64), also on
ghcr.io/kubevela/oamdev/terraform-controller. Chart 0.9.0 in https://kubevela.github.io/charts.

What's Changed

  • Update the link of kubevela project by @zzxwill in #386
  • Chore: upgrades Go (1.23.8) and K8s (1.31.0) versions by @roguepikachu in #396
  • Chore: upgrade go and k8s version by @PushparajShetty in #393
  • fix: pin ssh-agent socket path and resolve stale Configuration status on apply by @anishbista60 in #403
  • fix: clear remaining Snyk findings on bump-k8s by @roguepikachu in #406
  • chore: bump k8s client libraries and controller-runtime to v0.35.x line by @anishbista60 in #401
  • chore: bump go to 1.27.1, k8s deps to v0.37.1 and controller-runtime to v0.25.2 by @roguepikachu in #407
  • fix: delete the Terraform state lock lease when cleaning up the kubernetes backend by @vaibhav0096 in #408
  • [Backport release-0.9] chore: run CI on release branches, pin actions and build release candidates by @jerrinfrancis in #414
  • [Backport release-0.9] fix: move the controller to alpine 3.24 and pin its images for CVE-2026-111497 and the eMudhra CA by @jerrinfrancis in #418
  • [Backport release-0.9] fix: render jobNodeSelector as a JSON string in the chart by @jerrinfrancis in #426

The CI and fix changes landed on master in #413, #415, #417 and #425.

Full Changelog: v0.8.0...v0.9.0