Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up

Releases: fluxcd/flux2

v2.5.1

25 Feb 16:26
v2.5.1
This tag was signed with the committer’sverified signature.
stefanprodan Stefan Prodan
GPG key ID:3299AEB0E4085BAF
Verified
Learn about vigilant mode.
8d5f40d
This commit was created on GitHub.com and signed with GitHub’sverified signature.
GPG key ID:B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Loading

Highlights

Flux v2.5.1 is a patch release which comes with various fixes. Users are encouraged to upgrade for the best experience.

Fixes:

  • Fix a bug introduced in kustomize-controller v1.5.0 that was causing spurious logging for deprecated API versions and health check failures.
  • Sanitize the kustomize-controller logs when encountering errors during SOPS decryption.

Components changelog

CLI Changelog

Contributors

  • @matheuscscp
  • @fluxcdbot
matheuscscp and fluxcdbot
Assets19
stefanprodan, alialperak, mmmarceleza, uidmehdi, dmitriysafronov, and ebourgeois reacted with hooray emojisvengreb, githubcdr, and vugardzhamalov reacted with rocket emoji
9 people reacted

v2.5.0

20 Feb 14:35
v2.5.0
This tag was signed with the committer’sverified signature.
stefanprodan Stefan Prodan
GPG key ID:3299AEB0E4085BAF
Verified
Learn about vigilant mode.
af67405
This commit was created on GitHub.com and signed with GitHub’sverified signature.
GPG key ID:B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Loading

Highlights

Flux v2.5.0 is a feature release. Users are encouraged to upgrade for the best experience.

For a compressive overview of new features and API changes included in this release,
please refer to theAnnouncing Flux 2.5 GA blog post.

Overview of the new features:

  • Support for GitHub App authentication (GitRepository andImageUpdateAutomation API)
  • Custom Health Checks using CEL (Kustomization API)
  • Fine-grained control of garbage collection (Kustomization API)
  • Enable decryption of secrets generated by Kustomize components (Kustomization API)
  • Support for custom event metadata from annotations (Alert API)
  • Git commit status updates for Flux Kustomizations with OCIRepository sources (Alert API)
  • Resource filtering using CEL for webhook receivers (Receiver API)
  • Debug commands for Flux Kustomizations and HelmReleases (Flux CLI)

❤️ Big thanks to all the Flux contributors that helped us with this release!

Kubernetes compatibility

This release is compatible with the following Kubernetes versions:

Kubernetes versionMinimum required
v1.30>= 1.30.0
v1.31>= 1.31.0
v1.32>= 1.32.0

Note

Note that the Flux project offers support only for the latest three minor versions of Kubernetes.
Backwards compatibility with older versions of Kubernetes and OpenShift is offered by vendors such as
ControlPlane that provide enterprise support for Flux.

OpenShift compatibility

Flux can be installed on Red Hat OpenShift cluster directly from OperatorHub using
Flux Operator.
The operator allows the configuration of Flux multi-tenancy lockdown, network policies,
persistent storage, sharding, vertical scaling and the synchronization
of the cluster state from Git repositories, OCI artifacts and S3-compatible storage.

Upgrade procedure

Upgrade Flux fromv2.4.0 tov2.5.0 by following theupgrade guide.

There are no new API versions in this release, so no changes are required in the YAML manifests containing Flux resources.

Components changelog

CLI Changelog

Contributors

  • @mloskot
  • @scottrigby
  • @darkowlzz
  • @bkreitch
  • @milas
  • @jdewinne
  • @matheuscscp
  • @stefanprodan
  • @YvanGuidoin
  • @dependabot
  • @dipti-pai
  • @fluxcdbot
  • @h3nryc0ding
  • @sjorsholtrop-ritense
mloskot, scottrigby, and 12 other contributors
Loading
willianpaixao reacted with thumbs up emojirombert, sisid-github, kingdonb, netturpin, uderik, GreyXor, Alpenovsky, evandam, Kallepan, luis-giraldo, and 6 more reacted with hooray emojiHaveFun83, netturpin, uderik, meysam81, Jdavid77, judgeaxl, Alpenovsky, mmmarceleza, kodal, svengreb, and 4 more reacted with heart emojiinistor, HaveFun83, nathanielram, kingdonb, netturpin, uderik, Alpenovsky, svengreb, patsevanton, croneter, and 4 more reacted with rocket emoji
26 people reacted

v2.4.0

30 Sep 16:48
v2.4.0
This tag was signed with the committer’sverified signature.
stefanprodan Stefan Prodan
GPG key ID:3299AEB0E4085BAF
Verified
Learn about vigilant mode.
5350425
This commit was created on GitHub.com and signed with GitHub’sverified signature.
GPG key ID:B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Loading

Highlights

Flux v2.4.0 is a feature release. Users are encouraged to upgrade for the best experience.

For a comprehensive overview of new features and API changes included in this release, please refer to theAnnouncing Flux 2.4 GA blog post.

This release marks the General Availability (GA) of Flux Bucket API. TheBucket v1 API comes with new features including: proxy support, mTLS and custom STS configuration for AWS S3 and MinIO LDAP authentication.

TheGitRepository v1 API gains support for OIDC authentication. Starting with this version, you can authenticate against Azure DevOps repositories using AKS Workload Identity.

TheOCIRepository v1beta2 API gains support for proxy configuration thus allowing dedicated HTTP/S Proxy authentication on multi-tenant Kubernetes clusters.

TheHelmRelease v2 API gains support for disabling JSON schema validation of the Helm release values during installation and upgrade. And allows adopting existing Kubernetes resources during Helm release installation.

The Flux controllers are now built with Go 1.23 and their dependencies have been updated to Kubernetes 1.31, Helm 3.16, SOPS 3.9 Cosign 2.4 and Notation 1.2.

❤️ Big thanks to all the Flux contributors that helped us with this release!

Kubernetes compatibility

This release is compatible with the following Kubernetes versions:

Kubernetes versionMinimum required
v1.29>= 1.29.0
v1.30>= 1.30.0
v1.31>= 1.31.0

Note

Note that the Flux project offers support only for the latest three minor versions of Kubernetes.
Backwards compatibility with older versions of Kubernetes and OpenShift is offered by vendors such as
ControlPlane that provide enterprise support for Flux.

OpenShift compatibility

Flux can be installed on Red Hat OpenShift cluster directly from OperatorHub usingFlux Operator.
The operator allows the configuration of Flux multi-tenancy lockdown, network policies, persistent storage, sharding, vertical scaling and the synchronization of the cluster state from Git repositories, OCI artifacts and S3-compatible storage.

API changes

Bucket v1

TheBucket kind was promoted from v1beta2 to v1 (GA).

The v1 API is backwards compatible with v1beta2.

New fields:

  • .spec.proxySecretRef allows configuring HTTP/S Proxy authentication for the S3-compatible storage service.
  • .spec.certSecretRef allows custom TLS client certificate and CA for secure communication with the S3-compatible storage service.
  • .spec.sts allows custom STS configuration for AWS S3 and MinIO LDAP authentication.

GitRepository v1

TheGitRepository kind gains new optional fields with no breaking changes.

New fields:

  • .spec.provider allows specifying an OIDC provider used for authentication purposes. Currently, only theazure provider is supported.

OCIRepository v1beta2

TheOCIRepository kind gains new optional fields with no breaking changes.

New fields:

  • .spec.proxySecretRef allows configuring HTTP/S Proxy authentication for the container registry service.

HelmRelease v2

TheHelmRelease kind gains new optional fields with no breaking changes.

New fields:

  • .spec.install.disableSchemaValidation allows disabling the JSON schema validation of the Helm release values during installation.
  • .spec.upgrade.disableSchemaValidation allows disabling the JSON schema validation of the Helm release values during upgrade.

Upgrade procedure

Upgrade Flux fromv2.3.0 tov2.4.0 either byrerunning bootstrap or by using theFlux GitHub Action.

To upgrade the APIs, make sure the new CRDs and controllers are deployed, and then change the manifests in Git:

  1. SetapiVersion: source.toolkit.fluxcd.io/v1 in the YAML files that containBucket definitions.
  2. Commit, push and reconcile the API version changes.

Bumping the APIs version in manifests can be done gradually.
It is advised to not delay this procedure as the deprecated versions will be removed after 6 months.

Components changelog

New Documentation

CLI Changelog

Contributors

  • @nagyv
  • @bkreitch
  • @matheuscscp
  • @stefanprodan
  • @JasonTheDeveloper
  • @mxtw
  • @dipti-pai
  • @fluxcdbot
  • @harshitasao
nagyv, bkreitch, and 7 other contributors
Loading
ShadowUser17 reacted with thumbs up emojiaaparmeggiani, a1994sc, auricom, heubeck, mbaykara, adr1enbe4udou1n, gu1ll0me, luis-giraldo, cayla, laghoule, and 12 more reacted with hooray emojitimothystewart6, webwurst, cseeger-harris, Quicksilver-lab, svengreb, and willianpaixao reacted with heart emojisvengreb, Glaaj, and willianpaixao reacted with rocket emoji
27 people reacted

v2.3.0

13 May 13:55
v2.3.0
This tag was signed with the committer’sverified signature.
stefanprodan Stefan Prodan
GPG key ID:3299AEB0E4085BAF
Verified
Learn about vigilant mode.
896e0fa
This commit was created on GitHub.com and signed with GitHub’sverified signature.
GPG key ID:B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Loading

Highlights

Flux v2.3.0 is a feature release. Users are encouraged to upgrade for the best experience.

For a comprehensive overview of new features and API changes included in this release, please refer to theAnnouncing Flux 2.3 GA blog post.

This release marks the General Availability (GA) of Flux Helm features and APIs, including helm-controller, theHelmRelease,HelmChart, andHelmRepository APIs.

TheHelmRepository v2 API comes with new features, such as the ability to reference Helm charts fromOCIRepository sources, reuse existingHelmChart resources, and verify the integrity of Helm chart artifacts signed with Notary Notation.

❤️ Big thanks to all the Flux contributors that helped us with this release!

Kubernetes compatibility

This release is compatible with the following Kubernetes versions:

Kubernetes versionMinimum required
v1.28>= 1.28.0
v1.29>= 1.29.0
v1.30>= 1.30.0

Note

Note that the Flux project offers support only for the latest three minor versions of Kubernetes.
Backwards compatibility with older versions of Kubernetes and OpenShift is offered by vendors such as
ControlPlane that provide enterprise support for Flux.

API changes

HelmRelease v2

TheHelmRelease kind was promoted from v2beta2 to v2 (GA).

The v2 API is backwards compatible with v2beta2, with the exception of the deprecated fields which have been removed.

Removed fields:

  • .spec.chart.spec.valuesFile replaced by.spec.chart.spec.valuesFiles.
  • .spec.postRenderers.kustomize.patchesJson6902 replaced by.spec.postRenderers.kustomize.patches.
  • .spec.postRenderers.kustomize.patchesStrategicMerge replaced by.spec.postRenderers.kustomize.patches.
  • .status.lastAppliedRevision replaced by.status.history.chartVersion.

New fields:

  • .spec.chartRef allows referencing chart artifacts fromOCIRepository andHelmChart objects.
  • .spec.chart.spec.ignoreMissingValuesFiles allows ignoring missing values files instead of failing to reconcile.

HelmChart v1

TheHelmChart kind was promoted from v1beta2 to v1 (GA).

The v1 API is backwards compatible with v1beta2, with the exception of the deprecated fields which have been removed.

Removed fields:

  • .spec.valuesFile replaced by.spec.chart.valuesFiles.

New fields:

  • .spec.ignoreMissingValuesFiles allows ignoring missing values files instead of failing to reconcile.
  • .spec.verify.provider: notation verify the signature of a Helm OCI artifacts using Notation trust policy and CA certificate.

HelmRepository v1

TheHelmRepository kind was promoted from v1beta2 to v1 (GA).

The v1 API is backwards compatible with v1beta2.

OCIRepository v1beta2

TheOCIRepository kind gains new optional fields with no breaking changes.

New fields:

  • .spec.ref.semverFilter allows filtering the tags based on regular expressions before applying the semver range.
  • .spec.verify.provider: notation verify the signature of OCI artifacts using Notation trust policy and CA certificate.

Kustomization v1

The FluxKustomization kind gains new optional fields with no breaking changes.

New fields:

  • .spec.namePrefix allows setting a name prefix for the generated resources.
  • .spec.nameSuffix allows setting a name suffix for the generated resources.

ImageUpdateAutomation v1beta2

TheImageUpdateAutomation kind was promoted from v1beta1 to v1beta2.

The v1beta2 API is backwards compatible with v1beta1.

Deprecated fields:

  • Updated template data has been deprecated in favour ofChanged that is designed to accommodate for all the types of updates made.

New fields:

  • .spec.policySelector allows filteringImagePolicy based on labels.

Receiver v1

TheReceiver kind gains new optional fields with no breaking changes.

New fields:

  • .spec.type: cdevents allows receiving, validating and filtering of CDEvents.

Upgrade procedure

Upgrade Flux fromv2.x tov2.3.0 either byrerunning bootstrap or by using theFlux GitHub Action.

For more details, please refer to the upgrade guide from theAnnouncing Flux 2.3 GA blog post.

Components changelog

New Documentation

CLI Changelog

Read more

Contributors

  • @frekw
  • @carlpett
  • @makkes
  • @swade1987
  • @darkowlzz
  • @matheuscscp
  • @stefanprodan
  • @takp
  • @toomaj
  • @souleb
  • @dependabot
  • @JasonTheDeveloper
  • @twinguy
  • @rishinair11
  • @fluxcdbot
  • @hawwwdi
  • @adamkenihan
frekw, carlpett, and 15 other contributors
Loading
patsevanton, yuchang01, blop, kharf, willianpaixao, gdubroeucq, laiminhtrung1997, mlow, svengreb, ShadowUser17, and 2 more reacted with thumbs up emojisouleb, toledompm, patsevanton, a1994sc, blop, wr41th, dschniepp, heubeck, mbaykara, kharf, and 15 more reacted with hooray emojipatsevanton, blop, joaocc, cr1cr1, siegenthalerroger, spaceiq-vk, willianpaixao, laiminhtrung1997, carloscarnero, jack1902, and 2 more reacted with heart emojipatsevanton, blop, uidmehdi, kharf, jack-evans, Nielszy, pcanilho, willianpaixao, laiminhtrung1997, jack1902, and 3 more reacted with rocket emoji
39 people reacted

v2.2.3

05 Feb 14:44
v2.2.3
This tag was signed with the committer’sverified signature.
stefanprodan Stefan Prodan
GPG key ID:3299AEB0E4085BAF
Verified
Learn about vigilant mode.
5346846
This commit was created on GitHub.com and signed with GitHub’sverified signature.
GPG key ID:B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Loading

Highlights

Flux v2.2.3 is a patch release which comes with various fixes and improvements. Users are encouraged to upgrade for the best experience.

💡 For upgrading to Flux v2.2, please seethe procedure documented in 2.2.0.

This release updates the Kubernetes dependencies to v1.28.6 and various other dependencies to their latest version to patch upstream CVEs.

All controllers are built with Go 1.21.6 using Alpine Linux 3.19.1 base image.

Note

Due to breaking changes inHelm v3.14.0, the helm-controller version included in this patch release comes with Helm SDK v3.13.3.
A preview build of the helm-controller with the latest Helm SDK is available athelm-controller#879.

Fixes:

  • Reconciling empty directories and directories without Kubernetes manifests no longer results in an error. This regressing bug was introduced with the kustomize-controller upgrade to Kustomize v5.3 and has been fixed in this patch release.
  • The regression due to whichRoles andClusterRoles with aggregated roles were continuous reconciled by kustomize-controller has been fixed.
  • Fix the Git revision displaying when notification-controller sends alerts to Grafana.
  • The HelmRelease status reporting has been improved by ensuring that the stale failure conditions get updated after failure recovery.

See the components changelog for a full list of bug fixes.

Components changelog

CLI Changelog

Contributors

  • @darkowlzz
  • @stefanprodan
  • @dependabot
  • @twinguy
  • @fluxcdbot
darkowlzz, stefanprodan, and 3 other contributors
Loading
ShadowUser17 reacted with thumbs up emojiheubeck, mvilkki, tuxillo, mujak27, hprotzek, willianpaixao, mavogel, and TOHUHM reacted with hooray emojikingdonb, svengreb, ShinyaIshitobi, mvilkki, hprotzek, Hugh-yw, and willianpaixao reacted with rocket emojieabykov, meysam81, hprotzek, and willianpaixao reacted with eyes emoji
15 people reacted

v2.2.2

19 Dec 17:49
v2.2.2
This tag was signed with the committer’sverified signature.
hiddeco Hidde Beydals
GPG key ID:979F380FC2341744
Verified
Learn about vigilant mode.
5c5c15e
This commit was created on GitHub.com and signed with GitHub’sverified signature. The key has expired.
GPG key ID:4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Loading

Highlights

Flux v2.2.2 is a patch release that addresses an issue with the label selector sharding functionality in the helm-controller. Users are encouraged to upgrade for the best experience.

💡 For upgrading to Flux v2.2, please seethe procedure documented in 2.2.0.

Components changelog

CLI Changelog

Contributors

  • @hiddeco
  • @dependabot
  • @stuebingerb
  • @fluxcdbot
hiddeco, dependabot, and 2 other contributors
Loading
ShadowUser17 reacted with thumbs up emojirashedkvm, say5, and kamoljan reacted with hooray emoji
4 people reacted

v2.2.1

15 Dec 10:38
v2.2.1
This tag was signed with the committer’sverified signature.
hiddeco Hidde Beydals
GPG key ID:979F380FC2341744
Verified
Learn about vigilant mode.
9b39588
This commit was created on GitHub.com and signed with GitHub’sverified signature. The key has expired.
GPG key ID:4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Loading

Highlights

Flux v2.2.1 is a patch release that comes with fixes to API backwards compatibility.
Users are encouraged to upgrade for the best experience.

💡 For upgrading to Flux v2.2, please seethe procedure documented in 2.2.0.

This version was tested with the latest Kubernetes release, and extends Flux support to Kubernetes v1.29.

The Helm SDK was updated to the latest version, v3.13.3.

Logging in kustomize-controller and helm-controller has been improved to provide faster feedback on any HTTP errors encountered while fetching artifacts from source-controller.

Components changelog

CLI Changelog

Contributors

  • @stefanprodan
  • @hiddeco
  • @hoexter
  • @fluxcdbot
stefanprodan, hiddeco, and 2 other contributors
Loading
ShadowUser17 reacted with thumbs up emojiheubeck, seifrajhi, vperaltac, mavogel, cablespaghetti, and mvilkki reacted with hooray emojieabykov and seifrajhi reacted with eyes emoji
8 people reacted

v2.2.0

12 Dec 15:47
v2.2.0
This tag was signed with the committer’sverified signature.
stefanprodan Stefan Prodan
GPG key ID:3299AEB0E4085BAF
Verified
Learn about vigilant mode.
53ad742
This commit was created on GitHub.com and signed with GitHub’sverified signature. The key has expired.
GPG key ID:4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Loading

Highlights

Flux v2.2.0 is a feature release. Users are encouraged to upgrade for the best experience.

The Flux CLI and controllers have been updated to Kustomize v5.3.0 and Kubernetes v1.28.4.

Flux helm-controller's reconciliation model underwent a significant overhaul, addressing persistent issues such as the automatic recovery of releases stuck in a pending state. In addition, it improves the observability of the release status, and it introduces the ability to enable drift detection on a per-object basis. For more details on the helm-controller improvements, please see theAnnouncing Flux 2.2 GA blog post.

The Flux CLI can now be used to force or reset the reconciliation state of aHelmRelease v2beta2 object usingflux reconcile hr --force andflux reconcile hr --reset.

Flux CLI comes with support for bootstrappingGitea repositories and adds guardrails toflux install andflux bootstrap to protect users from destructive operations. Theflux version andflux check commands now print the Flux distribution version deployed on the cluster.

The Flux alerting capabilities have been extended withNATS andBitbucket Server & Data Center support.

Starting with this release, Flux minor versions are benchmark to measure the Mean Time To Production (MTTP). The results for this version can be found at
github.com/fluxcd/flux-benchmark.

❤️ Big thanks to all the Flux contributors that helped us with this release!

Kubernetes compatibility

This release is compatible with the following Kubernetes versions:

Kubernetes versionMinimum required
v1.26>= 1.26.0
v1.27>= 1.27.1
v1.28>= 1.28.0

Note that Flux may work on older versions of Kubernetes e.g. 1.25, but we don't recommend running end-of-life versions in production nor do we offer support for these versions.

API changes

HelmRelease v2beta2

TheHelmRelease kind was promoted from v2beta1 to v2beta2.

The v2beta2 API is backwards compatible with v2beta1, the v2beta1 API is deprecated and will be removed in a future release.

Deprecated fields:

  • The.patchesStrategicMerge and.patchesJson6902 Kustomize post-rendering fields have been deprecated in favor of.patches.
  • The.status.lastAppliedRevision and.status.lastReleaseRevision fields have been deprecated in favor of.status.history.
  • The.status.lastAttemptedValuesChecksum has been deprecated in favor of.status.lastAttemptedConfigDigest.

New fields:

  • Drift detection and correction is now enabled on a per-release basis using the.spec.driftDetection.mode field.
  • Ignoring specific fields during drift detection and correction is now supported using the.spec.driftDetection.ignore
  • Helm tests can now be selectively run using the.spec.test.filters field.
  • A history of metadata from Helm releases up to the previous successful release is now available in the.status.history field. This includes any Helm test results when enabled.
  • The.status.lastHandledForceAt and.status.lastHandledResetAt fields have been introduced to track the last time a force upgrade or reset was handled.

Alert and Provider v1beta3

TheAlert andProvider kinds were promoted from v1beta2 to v1beta3.

The v1beta3 API is backwards compatible with v1beta2, the.status field was removed making the resources static objects. Any errors encountered while sending notifications are now recorded as Kubernetes Events associated with the Alert objects.

Bucket v1beta2

A new field,.spec.prefix, has been added to theBucket API, which enables server-side filtering of files if the object's.spec.provider is set togeneric,aws orgcp.

OCIRepository and HelmChart v1beta2

Two new fields,.spec.verify.matchOIDCIdentity.issuer and.spec.verify.matchOIDCIdentity.subject have been added to theHelmChart andOCIRepository APIs. If the image has been keylessly signed via Cosign, these fields can be used to verify the OIDC issuer of the Fulcio certificate and the
OIDC identity's subject respectively.

HelmRepository and ImageRepository v1beta2

A new boolean field,.spec.insecure, has been introduced to the
HelmRepository andImageRepository APIs, which allows connecting to a non-TLS HTTP container registry. For HelmRepositories it is only considered if the object's.spec.type is set tooci.

From this release onwards, HelmRepository objects of type OCI are treated as static objects, i.e. they have an empty status.

Upgrade procedure

Upgrade Flux fromv2.x tov2.2.0 either byrerunning bootstrap or by using theFlux GitHub Action.

To upgrade the APIs, make sure the new CRDs and controllers are deployed, and then change the manifests in Git:

  1. SetapiVersion: helm.toolkit.fluxcd.io/v2beta2 in the YAML files that containHelmRelease definitions.
  2. SetapiVersion: notification.toolkit.fluxcd.io/v1beta3 in the YAML files that containAlert andProvider definitions.
  3. Commit, push and reconcile the API version changes.

Bumping the APIs version in manifests can be done gradually. It is advised to not delay this procedure as the deprecated versions will be removed after 6 months.

New Documentation

Components changelog

CLI Changelog

Read more

Contributors

  • @Skarlso
  • @Jaykul
  • @errordeveloper
  • @makkes
  • @darkowlzz
  • @matheuscscp
  • @stefanprodan
  • @VinGarcia
  • @sonbui00
  • @mclarke47
  • @hiddeco
  • @chewong
  • @souleb
  • @Azhovan
  • @somtochiama
  • @fluxcdbot
Skarlso, Jaykul, and 14 other contributors
Loading
yuchang01, hiddeco, mlow, qlimenoque, nianniansg, mavogel, sebbrandt87, patsevanton, and ShadowUser17 reacted with thumbs up emojiyuchang01, hiddeco, ThomasKat, mlow, vperaltac, qlimenoque, AlexandreMaldeme, heubeck, sebbrandt87, spencerrung, and 4 more reacted with hooray emojiyuchang01, hiddeco, mlow, dschniepp, kodek, sebbrandt87, patsevanton, svengreb, webwurst, cablespaghetti, and czhujer reacted with heart emojihiddeco, ThomasKat, mlow, sebbrandt87, spencerrung, patsevanton, svengreb, Xitric, and cablespaghetti reacted with rocket emojieabykov and patsevanton reacted with eyes emoji
23 people reacted

v2.1.2

12 Oct 13:57
v2.1.2
This tag was signed with the committer’sverified signature.
stefanprodan Stefan Prodan
GPG key ID:3299AEB0E4085BAF
Verified
Learn about vigilant mode.
a18d4f3
This commit was created on GitHub.com and signed with GitHub’sverified signature. The key has expired.
GPG key ID:4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Loading

Highlights

Fluxv2.1.2 is a patch release which comes with various fixes. Users are encouraged to upgrade for the best experience.

Fixes

  • Ensures faster recovery ofKustomization andHelmRelease resources when the source-controller has restarted and is working on restoring the storage.
  • Prevent source-controller from failing to reconcileOCIRepositories when artifacts contain symlinks.
  • Addresses issue with helm-controller miss-labeling Custom Resource Definitions.
  • Detect immutable field errors in Google Cloud resources managed by FluxKustomizations.
  • Better error reporting forflux bootstrap when the owner doesn't match the identity associated with the given token.
  • Allowflux pull artifact to fetch OCI artifacts produced by other tools.

Components changelog

CLI Changelog

Contributors

  • @Skarlso
  • @errordeveloper
  • @matheuscscp
  • @stefanprodan
  • @somtochiama
  • @fluxcdbot
Skarlso, errordeveloper, and 4 other contributors
Loading
ShadowUser17, mbaykara, antonioua, sandrotanner, Macbet, julanu, and grglzrv reacted with thumbs up emojiheubeck, HaveFun83, sandrotanner, grglzrv, spencerrung, and fbuchmeier reacted with hooray emojieabykov, Macbet, and grglzrv reacted with eyes emoji
12 people reacted

v2.1.1

19 Sep 11:56
v2.1.1
This tag was signed with the committer’sverified signature.
stefanprodan Stefan Prodan
GPG key ID:3299AEB0E4085BAF
Verified
Learn about vigilant mode.
026ab61
This commit was created on GitHub.com and signed with GitHub’sverified signature. The key has expired.
GPG key ID:4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Loading

Highlights

Fluxv2.1.1 is a patch release which comes with various fixes. Users are encouraged to upgrade for the best experience.

Fixes

  • Use auto lookup strategy for Buckets to widen support for S3-compatible object storage services (source-controller).
  • Fix Secret type check for HelmRepositories TLS certs referred in.spec.secretRef (source-controller).
  • Fix the branch name reporting when the push branch is the same as the checkout branch (image-automation-controller).
  • Restore Helm logs inclusion in failure events (helm-controller).
  • Fix the impersonation of the default service account when diffing HelmReleases (helm-controller).
  • Check source fornil artifact before loading Helm charts (helm-controller).
  • Update the description of Kubernetes specific flag to distinguish them from Flux bootstrap flags (flux CLI).

Components changelog

CLI Changelog

  • PR#4255 -@hiddeco - tests/azure: update controller dependencies
  • PR#4251 -@fluxcdbot - Update toolkit components
  • PR#4246 -@dependabot[bot] - build(deps): bump the ci group with 4 updates
  • PR#4238 -@makkes - Upgrade github.com/fluxcd/pkg/{git,git/gogit}
  • PR#4233 -@sonbui00 - chore: remove support armv6h for aur package
  • PR#4228 -@sonbui00 - Improve AUR package templates
  • PR#4227 -@dependabot[bot] - build(deps): bump the ci group with 3 updates
  • PR#4226 -@somtochiama - Update description of kubeconfig specific flag
  • PR#4222 -@dependabot[bot] - build(deps): bump github.com/cyphar/filepath-securejoin from 0.2.3 to 0.2.4 in /tests/integration
  • PR#4221 -@dependabot[bot] - build(deps): bump github.com/cyphar/filepath-securejoin from 0.2.3 to 0.2.4 in /tests/azure
  • PR#4215 -@dependabot[bot] - build(deps): bump the ci group with 4 updates
  • PR#4213 -@dependabot[bot] - build(deps): bump github.com/docker/distribution from 2.8.1+incompatible to 2.8.2+incompatible in /tests/integration
  • PR#4212 -@dependabot[bot] - build(deps): bump github.com/docker/docker from 23.0.1+incompatible to 23.0.3+incompatible in /tests/integration
  • PR#4198 -@makkes - Add 2.1.x backport label
  • PR#4197 -@stefanprodan - Fix links to fluxcd.io
  • PR#4195 -@dependabot[bot] - build(deps): bump the ci group with 2 updates

Contributors

  • @makkes
  • @stefanprodan
  • @sonbui00
  • @hiddeco
  • @dependabot
  • @somtochiama
  • @fluxcdbot
makkes, stefanprodan, and 5 other contributors
Loading
ShadowUser17, laghoule, svengreb, eabykov, and elvishsu66 reacted with thumbs up emojieabykov, HaveFun83, oscaromeu, and xunholy reacted with rocket emojieabykov reacted with eyes emoji
8 people reacted
Previous13451819
Previous

[8]ページ先頭

©2009-2025 Movatter.jp