Open and extensible continuous delivery solution for Kubernetes. Powered by GitOps Toolkit.
This is the 5th release candidate of Flux v2.0 GA. Users are advised to upgrade from older versions to v2.0.0-rc.5
as soon as possible.
Flux v2.0.0-rc.5
addresses a regression that was introduced in v2.0.0-rc.4
. This regression caused a disruption in the compatibility with Git servers utilizing v2 of the wire protocol, such as Azure Devops and AWS CodeCommit.
:bulb: For upgrading from v0.x, please see the procedure documented in RC.1.
⚠️ Note that v2.0.0-rc.4
updated all components to use Kustomize v5 and controller-runtime v0.15, both of which contain breaking changes.
[controller-runtime] log.SetLogger(...) was never called...
(CLI).controller-runtime
logger to a null loggerThis is the 4nd release candidate of Flux v2.0 GA. Users are advised to upgrade from older versions to v2.0.0-rc.4
as soon as possible.
Flux v2.0.0-rc.4 comes with support for Kustomize 5.0, Helm 3.12 and Cosign 2.0.
:bulb: For upgrading from v0.x, please see the procedure documented in RC.1.
⚠️ Note that Kustomize v5 contains breaking changes, please consult their changelog for more details.
⚠️ The GitOps Toolkit and the Flux controllers have been updated to controller-runtime v0.15 which contains breaking changes that could affect 3rd-party controllers that integrate with Flux.
flux reconcile source chart
for pulling Helm OCI charts on-demand from container registries (CLI).flux push artifact
(CLI)..spec.ref.name
in GitRepository
(source-controller).HelmRelease
events (notification-controller).This is the 3rd release candidate of Flux v2.0 GA. Users are advised to upgrade from v0.41
and older versions to v2.0.0-rc.3
as soon as possible.
Flux v2.0.0-rc.3 comes with security improvements, new features and fixes to issues reported for RC.2.
:bulb: For upgrading from v0.x, please see the procedure documented in RC.1.
:warning: Note that Kubernetes 1.27.0 contains a regression bug that affects Flux, it is recommended to upgrade Kubernetes to 1.27.1 or newer.
0o744
, allowing CI system to run them (source-controller).Alert
v1beta2 API has a new optional field .spec.eventMetadata
that allows users to enrich the alerts with information about the cluster name, region, environment, etc. (notification-controller).This is the 2nd release candidate of Flux v2.0 GA. Users are advised to upgrade from v0.41
to v2.0.0-rc.2
as soon as possible.
Flux v2.0.0-rc.2 comes with fixes to issues reported for RC.1 and performance improvements. Starting with this version, source-controller, kustomize-controller and helm-controller pods are marked as system-cluster-critical. This priority class will reduce the chances of Flux controllers being evicted before other non-critical workloads and prevents the pods from being permanently unavailable.
:bulb: For upgrading from v0.x, please see the procedure documented in RC.1.
:warning: Note that Kubernetes 1.27.0 contains a regression bug that affects Flux, it is recommended to upgrade Kubernetes to 1.27.1 or newer.
Alert
v1beta2 API has a new optional field .spec.inclusionList
for fine-grained control over events filtering (notification-controller)..status.url
was removed from the Receiver
v1 API (notification-controller).pull artifact
commandThis is the first release candidate of Flux v2.0 GA :tada:. Users are encouraged to upgrade for the best experience.
Flux v2.0.0-rc.1 comes with the promotion of the GitOps related APIs to v1 and adds horizontal scaling & sharding capabilities to Flux controllers.
In addition, RC.1 comes with support for auth with Azure Workload Identity when pulling OCI artifacts from ACR and when decrypting secret with Azure Vault. Also, Bootstrap for GitLab was extended with support for generating GitLab Deploy Tokens.
:heart: Big thanks to all the Flux contributors that helped us with this release! 👏 And a special shoutout to the GitLab team for their first contribution to Flux!
The GitRepository kind was promoted from v1beta2 to v1 (GA) and deprecated fields were removed.
The v1 API is backwards compatible with v1beta2, except for the following:
.spec.gitImplementation
was removed.spec.accessFrom
was removed.status.contentConfigChecksum
was removed.status.artifact.checksum
was removed.status.url
was removed in favor of the absolute .status.artifact.url
The Kustomization kind was promoted from v1beta2 to v1 (GA) and deprecated fields were removed.
A new optional field .spec.commonMetadata
was added to the API for setting labels and/or annotations to all resources part of a Kustomization.
The v1 API is backwards compatible with v1beta2, except for the following:
.spec.validation
was removed.spec.patchesStrategicMerge
was removed (replaced by .spec.patches
).spec.patchesJson6902
was removed (replaced by .spec.patches
)The Receiver kind was promoted from v1beta2 to v1 (GA).
The v1 API now supports triggering the reconciliation of multiple resources using .spec.resources.matchLabels
.
The v1 API is backwards compatible with v1beta2, no fields were removed.
Upgrade Flux from v0.x
to v2.0.0-rc-1
either by rerunning flux bootstrap or by using the Flux GitHub Action.
To upgrade the APIs from v1beta2, after deploying the new CRDs and controllers, change the manifests in Git:
GitRepository
and Kustomization
definitions.apiVersion: source.toolkit.fluxcd.io/v1
in the YAML files that contain GitRepository
.apiVersion: kustomize.toolkit.fluxcd.io/v1
in the YAML files that contain Kustomization
.apiVersion: notification.toolkit.fluxcd.io/v1
in the YAML files that contain Receiver
definitions.Bumping the APIs version in manifests can be done gradually. It is advised to not delay this procedure as the beta versions will be removed after 6 months.
:warning: Note that this release updates the major version of the Flux Go Module to v2. Please update your go.mod
to require github.com/fluxcd/flux2/v2
, see pkg.go.dev for the documentation of the module.
Flux v0.41.2 is a patch release which fixes a range of bugs found in the controllers. Please refer to the individual component changelogs for more information.
:bulb: For more information about other features introduced in v0.41.0, please refer to the changelog for this version.
actions/setup-go
in workflowsFlux v0.41.1 is a patch release which extends the helm-controller's OOM watch feature introduced in v0.41.0 with support for automatic detection of cgroup v1 paths, and flags to configure alternative paths using --oom-watch-max-memory-path
and --oom-watch-current-memory-path
.
:bulb: For more information about other features introduced in v0.41.0, please refer to the changelog for this version.
Flux v0.41.0 comes with new features and improvements. Users are encouraged to upgrade for the best experience.
SIGTERM
signals received by the helm-controller, which will now terminate running Helm install or upgrade actions, instead of potentially leaving them in a pending state.flux events
command to display Kubernetes events for Flux resources, including the events of a referenced resource.flux push
using --annotations
.flux events
commandFlux v0.40.2 is a patch release which includes an update of the notification-controller to prevent an issue with the default API version used for ImageRepositories when no specific version is configured on a Receiver. Users are encouraged to upgrade for the best experience.
:warning: Note that v0.40.0 contained breaking changes, please refer to the changelog for more information.
Flux v0.40.1 is a patch release which includes an update of the source-controller to prevent excessive memory usage while reconciling HelmRepository objects. Users are encouraged to upgrade for the best experience.
:warning: Note that v0.40.0 contained breaking changes, please refer to the changelog for more information.