Skip to content

chore(deps): update module github.com/fluxcd/helm-operator to v1.4.0 - autoclosed

SWE Renovate requested to merge renovate/github.com-fluxcd-helm-operator-1.x into master

This MR contains the following updates:

Package Type Update Change
github.com/fluxcd/helm-operator require minor v1.2.0 -> v1.4.0

Release Notes

fluxcd/helm-operator

v1.4.0

Compare Source

Note: Breaking Changes

This release of Helm Operator will break compatibility with older releases of Kubernetes, in order to ensure forward compatibility with long-awaited breaking changes in Kubernetes 1.22.0.

The v1beta1 release of CustomResourceDefinition as well as Role, ClusterRole, and role bindings, have been replaced by their v1 counterparts, and will finally be removed.

Helm Operator and Flux are in maintenance: Efforts have been focused on the next generation of Flux, also called the GitOps Toolkit, which has crossed the feature-parity milestone, and is already recommended for production use in many cases. The helm-controller is the replacement for Helm Operator. The roadmap for Flux v2 development including Helm Controller can be found here.

We are eager to hear feedback, suggestions, and/or feature requests for the helm-controller and other Toolkit components. The migration timetable will be kept updated with developments regarding the ongoing support of Helm Operator.

Users of Helm Operator should be planning or executing their migrations, and report any blocking issues so that they can be addressed as early as possible.

NOTE: Make sure to update the CRD when upgrading from a previous version as they have been changed since the prior release.

Please note, while we continue the Helm Operator support, there are some known issues in Helm Operator that cannot be addressed. Users are advised strongly to plan their infrastructure upgrades and migrate to Flux v2 and Helm Controller as soon as possible, as Helm Operator will soon no longer be maintained.

Maintenance

v1.3.0

Compare Source

Helm Operator and Flux are in maintenance: Efforts have been focused on the next generation of Flux, also called the GitOps Toolkit, which has crossed the feature-parity milestone, and is already recommended for production use in many cases. The helm-controller is the replacement for Helm Operator. The roadmap for Flux v2 development including Helm Controller can be found here.

We are eager to hear feedback, suggestions, and/or feature requests for the helm-controller and other Toolkit components. The migration timetable will be kept updated with developments regarding the ongoing support of Helm Operator.

Users of Helm Operator should be planning their migrations, and report any blocking issues so that they can be addressed as early as possible.

NOTE: Make sure to update the CRD when upgrading from a previous version as they may have been changed since the prior release.

Documentation for Helm Operator has moved under fluxcd.io/legacy/flux. This release includes any merged fixes that were unreleased for the past year, including an upgrade from Helm 3.1.x to Helm 3.5.4 which also covered some breaking changes in Helm.

The next MINOR (1.4.0) release of Helm Operator will break compatibility with older releases of Kubernetes, in order to ensure forward compatibility with long-awaited breaking changes in Kubernetes 1.22.0.

(fluxcd/helm-operator#​599 and fluxcd/helm-operator#​618 describe the breaking changes that are upcoming in Helm Operator 1.4.0.)

Please note, this is a security update and while we continue the Helm Operator support, there are some known issues in Helm Operator that cannot be addressed. (From testing 1.4.0-RC1 via #​626, Helm Plugins are known to be likely broken.)

Users are advised strongly to plan their infrastructure upgrades and migrate to Flux v2 and Helm Controller as soon as possible, as Helm Operator will soon no longer be maintained.

Maintenance
Enhancements
Fixes
Documentation
Thanks

Thanks to @​Carles-Figuerola, @​amit-handda, @​bmalynovytch, @​coultenholt, @​dholbach, @​em-schmidt, @​flimzy, @​fredr, @​hiddeco, @​jbuettnerbild, @​kingdonb, @​krichardson-apexclearing, @​mattjw, @​mbrancato, @​mnaser, @​neil-greenwood, @​nilesh892003, @​smarthall, @​stefanprodan, @​swade1987, @​t1bb4r, @​tux-00 and @​wujiangfa-xlauncher for their contributions to this release.

Configuration

📅 Schedule: 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 this update again.

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

This MR has been generated by Renovate Bot.

Edited by SWE Renovate

Merge request reports