NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules, #3112 by repository stars
Latest stable
v1.10.1
Last release 19 days ago
03 Nov 2026
Ships fairly regularly
a new release about every 2 weeks
Nearly every release is documented
notes for 60 of the last 60 stable releases
1 version withdrawn
withdrawn after publishing
7 years old
516 releases · first in 2020
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
docker.io/fluxcd/source-controller:v1.0.0
docker.io/fluxcd/source-controller:v1.0.0ghcr.io/fluxcd/source-controller:v1.0.0Supported architectures: linux/amd64, linux/arm64 and linux/arm/v7.
The container images are built on GitHub hosted runners and are signed with cosign and GitHub OIDC. To verify the images and their provenance (SLSA level 3), please see the security documentation.
Release date: 2023-07-03
This is the first stable release of the controller. From now on, this controller follows the Flux 2 release cadence and support pledge.
Starting with this version, the build, release and provenance portions of the Flux project supply chain provisionally meet SLSA Build Level 3.
This release includes several minor changes that primarily focus on addressing forgotten and obsolete bits in the logic related to GitRepository objects.
Including a removal of the OptimizedGitClones feature flag. If your
Deployment is configured to disable this flag, you should remove it.
In addition, dependencies have been updated to their latest version, including an update of Kubernetes to v1.27.3.
For a comprehensive list of changes since v0.36.x, please refer to the
changelog for v1.0.0-rc.1, v1.0.0-rc.3 and
v1.0.0-rc.4.
Improvements:
Nothing published for this version
Nothing published for this version
CHANGELOG
Release date: 2023-06-01
This release candidate fixes a regression introduced in 1.0.0.-rc.4 where
support for Git servers that exclusively use v2 of the wire protocol like Azure
Devops and AWS CodeCommit was broken.
Lastly, the controller's dependencies were updated to mitigate CVE-2023-33199.
Improvements:
Fixes:
fluxcd/pkg/git/gogit to v0.12.0
#1111Nothing published for this version
Nothing published for this version
CHANGELOG
Release date: 2023-05-26
This release candidate comes with support for Kubernetes v1.27 and Cosign v2.
It also enables the use of annotated Git tags with .spec.ref.name in
GitRepository. Furthermore, it fixes a bug related to accessing Helm OCI
charts on ACR using OIDC auth.
Improvements:
go-git/go-git and pkg/tar
#1105CHANGELOG
Release date: 2023-05-12
This release candidate introduces the verification of the Artifact digest in storage during reconciliation. This ensures that the Artifact is not tampered with after it was written to storage. When the digest does not match, the controller will emit a warning event and remove the file from storage, forcing the Artifact to be re-downloaded.
In addition, files with executable permissions are now archived with their mode
set to 0o744 instead of 0o644. Allowing the extracted file to be executable
by the user.
Lastly, the controller's dependencies were updated to mitigate CVE-2023-1732 and CVE-2023-2253, and the controller base image was updated to Alpine 3.18.
Improvements:
Nothing published for this version
CHANGELOG
Release date: 2023-05-09
This release candidate comes with various updates to the controller's dependencies, most notable, Helm was updated to v3.11.3.
Improvements:
Nothing published for this version
Nothing published for this version
Nothing published for this version
CHANGELOG
Release date: 2023-03-30
This release candidate promotes the GitRepository API from v1beta2 to v1.
The controller now supports horizontal scaling using
sharding based on a label selector.
In addition, support for Azure Workload Identity was added to
OCIRepositories, Buckets and HelmRepositories when using provider: azure.
The GitRepository kind was promoted from v1beta2 to v1 (GA) and deprecated fields were removed.
The common types Artifact, Conditions and the Source interface were promoted to v1.
The gitrepositories.source.toolkit.fluxcd.io CRD contains the following versions:
The GitRepository 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.urlTo upgrade from v1beta2, after deploying the new CRD and controller,
set apiVersion: source.toolkit.fluxcd.io/v1 in the YAML files that
contain GitRepository definitions and remove the deprecated fields if any.
Bumping the API 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.
Starting with this release, the controller can be configured with
--watch-label-selector, after which only objects with this label will
be reconciled by the controller.
This allows for horizontal scaling, where source-controller can be deployed multiple times with a unique label selector which is used as the sharding key.
Note that this also requires configuration of the --storage-adv-addr
to a unique address (in combination with a proper Service definition).
This to ensure the Artifacts handled by the sharding controller point
to a unique endpoint.
In addition, Source object kinds which have a dependency on another kind (i.e. a HelmChart on a HelmRepository) need to have the same labels applied to work as expected.
Improvements:
Nothing published for this version
CHANGELOG
Release date: 2023-03-20
This release fixes a bug where after reading a .sourceignore file in a
subdirectory, the controller could start to ignore files from directories next
to the directory the .sourceignore file was placed in.
Fixes:
Nothing published for this version
CHANGELOG
Release date: 2023-03-08
This release changes the format of the Artifact Revision field when using a
GitRepository with a .spec.ref.name set (introduced in v0.35.0),
changing it from sha1:<commit> to <name>@sha1:<commit>. Offering a more
precise reflection of the revision the Artifact was created from.
In addition, klog is now configured to log using the same logger as the rest
of the controller (providing a consistent log format).
Lastly, the controller is now built using Go 1.20, and the dependencies have
been updated to their latest versions.
Improvements:
CHANGELOG
Release date: 2023-02-23
This release reduces the amount of memory consumed by the controller when
reconciling HelmRepositories, by using only the digest of the YAML file as the
Revision of the Artifact instead of the stable sorted version of the entire
index. This aligns with the behavior before v0.35.0, and is therefore
considered a bug fix.
In addition, the dependencies have been updated to include some minor security patches.
Note that v0.35.0 contains breaking changes. Please refer to the changelog
entry for more information.
Fixes:
Improvements:
CHANGELOG
Release date: 2023-02-17
This release addresses a hypothetical issue with the Artifact Digest field
validation, where a patch of the Artifact could fail to be applied to an object
due to the lack of an omitempty tag on the optional field. In reality, this
issue is not possible to encounter, as the Digest field is always set when
the Artifact is created.
Note that v0.35.0 contains breaking changes. Please refer to the changelog
entry for more information.
Fixes:
Nothing published for this version
CHANGELOG
Release date: 2023-02-16
This release introduces a new format for the Artifact Revision, and deprecates
the Checksum field in favor of a new Digest field. In addition, it adds
support for Git reference names in a GitRepository, and comes with the usual
collection of dependency updates.
Starting with this version, it is possible to define a Git Reference
in a GitRepository using .spec.ref.name.
This opens the door to a range of functionalities not available before, as it
for example allows the controller to follow pull (refs/pull/<id>/head) or
merge (refs/merge-requests/<id>/head) requests, and allows a transition from
the HEAD of a branch (refs/heads/main) to a tag (refs/tags/v0.1.0) by
changing a single field value.
Refer to the GitRepository specification for more details.
The Artifact of a Source will now advertise a Digest field containing the
checksum of the file advertised in the Path, and the alias of the algorithm
used to calculate it. Creating a "digest" in the format of <algo>:<checksum>.
The algorithm is configurable using the newly introduced --artifact-digest-algo
flag, which allows configuration of other algorithms (sha384, sha512, and
blake3) than the hardcoded sha256 default of the now deprecated Checksum
field.
Please note that until the Checksum is fully deprecated, changing the
algorithm is not yet advised (albeit supported), as this will result in a
double computation.
The Revision format for an Artifact consisting of a named pointer (a Git
branch or tag) and/or a specific revision (a Git commit SHA or other calculated
checksum) has changed to contain an @ separator opposed to /, and includes
the algorithm alias as a prefix to a checksum (creating a "digest").
In addition, HEAD is no longer used as a named pointer for exact commit
references, but will now only advertise the commit itself.
For example:
main/1eabc9a41ca088515cab83f1cce49eb43e84b67f => main@sha1:1eabc9a41ca088515cab83f1cce49eb43e84b67fHEAD/5394cb7f48332b2de7c17dd8b8384bbc84b7e738 => sha1:5394cb7f48332b2de7c17dd8b8384bbc84b7e738tag/55609ff9d959589ed917ce32e6bc0f0a36809565f308602c15c3668965979edc => tag@sha256:55609ff9d959589ed917ce32e6bc0f0a36809565f308602c15c3668965979edc8fb62a09c9e48ace5463bf940dc15e85f525be4f230e223bbceef6e13024110c => sha256:8fb62a09c9e48ace5463bf940dc15e85f525be4f230e223bbceef6e13024110cWhen the storage of the controller is backed by a Persistent Volume, the rollout of this new format happens for the next new revision the controller encounters. Otherwise, the new revision will be advertised as soon as the Artifact has been reproduced after the controller is deployed.
Other Flux controllers making use of an Artifact are aware of the change in
format, and work with it in a backwards compatible manner. Avoiding observing
a change of revision when this is actually just a change of format. If you
programmatically make use of the Revision, please refer to the
TransformLegacyRevision helper
to allow a transition period in your application.
For more information around this change, refer to RFC-0005.
The Checksum field of an Artifact has been deprecated in favor of the newly
introduced Digest. Until the deprecated field is removed in the next version
of the API, the controller will continue to produce the SHA-256 checksum in
addition to the digest. Changing the algorithm used to produce the digest using
--artifact-digest-algo is therefore not yet advised (albeit supported), as
this will result in a double computation.
For more information around this change, refer to RFC-0005.
Improvements:
Fixes:
Nothing published for this version
Nothing published for this version
CHANGELOG
Release date: 2023-01-31
This prerelease comes with support for HTTPS bearer token authentication for Git
repository. The GitRepository authentication Secret is expected to contain the
bearer token in .data.bearerToken.
The caching of Secret and ConfigMap resources is disabled by
default to improve memory usage. To opt-out from this behavior, start the
controller with: --feature-gates=CacheSecretsAndConfigMaps=true.
All the Source kinds now support progressive status updates. The progress made by the controller during reconciliation of a Source is reported immediately in the status of the Source object.
In addition, the controller dependencies have been updated to Kubernetes v1.26.
:warning: Breaking change: When using SSH authentication in GitRepository,
if the referenced Secret contained .data.username, it was used as the SSH
user. With this version, SSH user will be the username in the SSH address. For
example, if the Git repository address is ssh://flux@example.com, flux will
be used as the SSH user during SSH authentication. When no username is
specified, git remains the default SSH user.
Improvements:
Nothing published for this version
CHANGELOG
Release date: 2022-12-20
This prerelease comes with dedicated mux for the controller's fileserver. All code references to libgit2 were removed, and the spec.gitImplementation
field is no longer being honored, but rather go-git is used.
For more information, refer to version 0.32.0's changelog, which started libgit2's
deprecation process.
The controller's garbage collection now takes into consideration lock files.
The feature gate ForceGoGitImplementation was removed, users passing it as their
controller's startup args will need to remove it before upgrading.
Fixes:
Improvements:
CHANGELOG
Release date: 2022-11-18
This prerelease rectifies the v0.32.0 release by retracting the previous Go
version, bumping the controller api version and the controller deployment.
CHANGELOG
Release date: 2022-11-17
This prerelease comes with a major refactoring of the controller's Git operations.
The go-git implementation now supports all Git servers, including
Azure DevOps, which previously was only supported by libgit2.
This version initiates the soft deprecation of the libgit2 implementation.
The motivation for removing support for libgit2 being:
libgit2 implementation, which
is a C library called via CGO through git2go, it will never perform as well as
a pure Go implementations. At scale, memory pressure insues which then triggers
the reliability issues above.libgit2, we have to maintain an additional repository. Statically built
libgit2 libraries need to be cross-compiled for all our supported platforms.
And a lot of "unnecessary" code has to be in place to make building, testing and
fuzzing work seamlessly.As a result the field spec.gitImplementation is ignored and the
reconciliations will use go-git. To opt-out from this behaviour, start
the controller with: --feature-gates=ForceGoGitImplementation=false.
Users having any issues with go-git should report it to the Flux team,
so any issues can be resolved before support for libgit2 is completely
removed from the codebase.
Improvements:
Nothing published for this version
CHANGELOG
Release date: 2022-10-21
This prerelease comes with support for Cosign verification of Helm charts.
The signatures verification can be configured by setting HelmChart.spec.verify with
provider as cosign and a secretRef to a secret containing the public key.
Cosign keyless verification is also supported, please see the
HelmChart API documentation
for more details.
In addition, the controller dependencies have been updated to Kubernetes v1.25.3 and Helm v3.10.1.
Improvements:
Fixes:
Nothing published for this version
Nothing published for this version
CHANGELOG
Release date: 2022-10-10
This prerelease enables the use of container-level SAS tokens when using Bucket objects
to access Azure Storage. The Azure SDK error message has also been enriched to hint Flux
users the potential reasons in case of failure.
Improvements:
CHANGELOG
Release date: 2022-09-29
This prerelease adds support for Cosign verification in OCIRepository source.
The signatures verification can be configured by setting OCIRepository.spec.verify with
provider as cosign and a secretRef to a secret containing the public key.
Cosign keyless verification is also supported, please see the
OCIRepository API documentation
for more details.
It also comes with strict validation rules for API fields which define a
(time) duration. Effectively, this means values without a time unit (e.g. ms,
s, m, h) will now be rejected by the API server. To stimulate sane
configurations, the units ns, us and µs can no longer be configured, nor
can h be set for fields defining a timeout value.
In addition, the controller dependencies have been updated to Kubernetes controller-runtime v0.13.
:warning: Breaking changes:
.spec.interval new validation pattern is "^([0-9]+(\\.[0-9]+)?(ms|s|m|h))+$".spec.timeout new validation pattern is "^([0-9]+(\\.[0-9]+)?(ms|s|m))+$"Improvements:
Fixes:
Nothing published for this version
CHANGELOG
Release date: 2022-09-09
This prerelease adds support for non-TLS container registries such
as Kubernetes Kind Docker Registry.
Connecting to an in-cluster registry over plain HTTP,
requires setting the OCIRepository.spec.insecure field to true.
:warning: Breaking change: The controller logs have been aligned with the Kubernetes structured logging. For more details on the new logging structure please see: fluxcd/flux2#3051.
Improvements:
Fixes:
Nothing published for this version
CHANGELOG
Release date: 2022-08-29
This prerelease adds support for contextual login to container registries when pulling
Helm charts from Azure Container Registry, Amazon Elastic Container Registry
and Google Artifact Registry. Contextual login for HelmRepository
objects can be enabled by setting the spec.provider field to azure, aws or gcp.
Selecting the OCI layer containing Kubernetes manifests is now possible
when defining OCIRepository objects by setting the spec.layerSelector.mediaType field.
In addition, the controller dependencies have been updated to Kubernetes v1.25.0 and Helm v3.9.4.
Improvements:
Nothing published for this version
Nothing published for this version
CHANGELOG
Release date: 2022-08-17
This prerelease adds support for SAS Keys when authenticating against Azure Blob Storage
and improves the documentation for OCIRepository.
The package sourceignore, which is used for excluding files from Flux internal artifacts,
has been moved to fluxcd/pkg/sourceignore.
Improvements:
CHANGELOG
Release date: 2022-08-11
This prerelease comes with panic recovery, to protect the controller from crashing when reconciliations lead to a crash. It also adds OCI documentation and improvements to the controllers CI pipeline.
Improvements:
CHANGELOG
Release date: 2022-08-08
This prerelease comes with a new API kind named OCIRepository,
for fetching OCI artifacts from container registries as defined in
RFC-0003 Flux OCI support for Kubernetes manifests.
Please see the
OCIRepository API documentation
for more details.
In addition, Helm charts stored in Git can now have dependencies to other charts stored as OCI artifacts in container registries.
Features:
Improvements:
Fixes:
CHANGELOG
Release date: 2022-07-27
This prerelease comes with an improvement in the Helm OCI Chart to use an exact version when provided. This makes it possible to work with registries that don't support listing tags.
Improvements:
CHANGELOG
Release date: 2022-07-13
This prerelease fixes SIGSEGV when resolving charts dependencies. It also brings CI improvements and update dependencies to patch upstream CVEs.
Fixes:
Improvements:
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
One column per quarter.