Skip to content

chore(deps): update dependency fluxcd/flux2 to v0.38.2

Botaniker (Bot) requested to merge renovate/fluxcd-flux2-0.x into main

This MR contains the following updates:

Package Update Change
fluxcd/flux2 minor v0.36.0 -> v0.38.2

Release Notes

fluxcd/flux2

v0.38.2

Compare Source

Flux v0.38.2 is a patch release that comes with fixes for the Notification API v1beta1 to v1beta2 upgrade. In addition, this release improves the handling of the graceful shutdown for helm-controller. Users are encouraged to update Flux directly to v0.38.2 for the best experience.

Components changelog
CLI Changelog

v0.38.1

Compare Source

Flux v0.38.1 is a patch release that comes with fixes for the Notification API v1beta1 to v1beta2 upgrade. Users are encouraged to update Flux directly to v0.38.1 for the best experience.

Changelog

v0.38.0

Compare Source

Highlights

Flux v0.38.0 comes with new features and improvements. Users are encouraged to upgrade for the best experience.

Notification API v1beta2

This release graduates the Notification APIs to v1beta2. After upgrading the controllers on your clusters, you need to update the notification Custom Resources in Git by replacing notification.toolkit.fluxcd.io/v1beta1 with notification.toolkit.fluxcd.io/v1beta2 in all YAML manifests.

Breaking changes
  • The Alert.spec.summary has a max length of 255 characters.
  • The Provider.spec.address and Provider.spec.proxy have a max length of 2048 characters.
  • The Receiver.status.url was deprecated in favour of Receiver.status.webhookPath.

For more details about v1beta2 please see the notification-controller chagelog and the API spec documentation.

Features and improvements
  • Support for defining Kustomize components with Kustomization.spec.components.
  • Support for piping multi-doc YAMLs when publishing OCI artifacts with kustomize build . | flux push artifact --path=-.
  • Support for Gitea commit status updates with Provider.spec.type set to gitea.
  • Improve the memory usage of helm-controller by disabling the caching of Secret and ConfigMap resources.
  • Update the Helm SDK to v3.10.3 (fix for Helm CVEs).
  • All code references to libgit2 were removed, and the GitRepository.spec.gitImplementation field is no longer being honored.
Documentation improvements

The official example repository was refactored. The new version comes with the following improvements:

  • Make the example compatible with ARM64 Kubernetes clusters.
  • Add Weave GitOps Helm release to showcase the Flux UI.
  • Replace the ingress-nginx Bitnami chart with the official one that contains multi-arch container images.
  • Add cert-manager Helm release to showcase how to install CRDs and custom resources using dependsOn.
  • Add Let's Encrypt ClusterIssuer to showcase how to patch resources in production with Flux Kustomization.
  • Add the flux-system overlay to showcase how to configure Flux at bootstrap time.
Components changelog
CLI Changelog

v0.37.0

Compare Source

Highlights

Flux v0.37.0 comes with new features and improvements. Users are encouraged to upgrade for the best experience.

Breaking changes
Deprecation of gitImplementation

The interpretation of the gitImplementation field of GitRepository by source-controller and image-automation-controller has been deprecated, and will effectively always use go-git. This now supports all Git servers, including Azure DevOps and AWS CodeCommit, which previously were only supported by libgit2.

To opt-out from this behaviour, and get the controller to honour the field .spec.gitImplementation, start the controller with: --feature-gates=ForceGoGitImplementation=false.

For more information on this change, refer to the controllers's respective changelogs listed below.

Automatic force-push of ImageUpdateAutomation

Starting from this version, ImageUpdateAutomation objects with a .spec.PushBranch specified will have the push branch refreshed automatically via force push. To opt-out from this behaviour, start the controller with: --feature-gates=GitForcePushBranch=false.

Features and improvements
  • Support for bootstrapping Azure DevOps and AWS CodeCommit repositories using flux bootstrap git.
  • Support cloning of Git v2 protocol (Azure DevOps and AWS CodeCommit) for go-git Git provider.
  • Support force-pushing ImageUpdateAutomation repositories.
  • Allow a dry-run of flux build kustomization with --dry-run and --kustomization-file ./path/to/local/my-app.yaml. Using these flags, variable substitutions from Secrets and ConfigMaps are skipped, and no connection to the cluster is made.
  • Use signed OCI Helm chart for kube-prometheus-stack.
New documentation

Components changelog

CLI Changelog

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about these updates again.

  • If you want to rebase/retry this MR, check this box

This MR has been generated by Renovate Bot. The local configuration can be found in the SI Renovate Bot repository.

Edited by Botaniker (Bot)

Merge request reports