Skip to content

v1.3.0

Choose a tag to compare

@Shivs11 Shivs11 released this 10 Mar 14:10
· 64 commits to main since this release

Warning

This release is unstable and should not be used in production.

Helm chart versions <0.20.0 were built using manifests from the main branch at release time instead of the release branch. As a result, deployed manifests may not match the expected code version.

Required action:
Upgrade to v1.3.1 (Helm Chart 0.20.0). This is the first version with corrected manifests and a tested upgrade path from affected releases.

Recommended next step:
After upgrading to v1.3.1, continue upgrading to the latest GA release (v1.7.0) for production use.
For production environments, upgrade one minor version at a time after 0.20.0.
See docs/release.md for full details on versioning and upgrade paths.


Warning

This release is unstable and should not be used in production.
PR #212 introduced a bug in TLS certificate handling.
The issue is fixed in #227.

Recommended action: Skip this version and upgrade to the release containing the fix.


What's Changed

  • Adding a CI action to validate helm chart renderings by @Shivs11 in #199
  • Helm chart bug Fix: Make sure image has nonRoot by @Shivs11 in #195
  • fix: use CA certificate from mTLS secret for server verification by @Shivs11 in #212
  • Bump golang.org/x/crypto from 0.37.0 to 0.45.0 by @dependabot[bot] in #185
  • Bump filippo.io/edwards25519 from 1.1.0 to 1.1.1 in /internal/tests by @dependabot[bot] in #201
  • Bump filippo.io/edwards25519 from 1.1.0 to 1.1.1 by @dependabot[bot] in #202
  • Add event recording and status conditions for worker deployments by @thearcticwatch in #203
  • Bump go.opentelemetry.io/otel/sdk from 1.34.0 to 1.40.0 by @dependabot[bot] in #213
  • Add CI check to verify Helm chart image references are pullable by @carlydf in #222
    • This PR replaces the deprecated gcr.io/kubebuilder/kube-rbac-proxy:v0.14.1 image with registry.k8s.io/kubebuilder/kube-rbac-proxy:v0.14.1, and adds a CI check to ensure that this issue won't happen in the future.
  • Shorten deployment names when over 47 characters by @carlydf in #204

New Contributors

Full Changelog: v1.2.0...v1.3.0