Skip to content

fix(github-release): update flux group to v2.0.1 (patch)#64

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/patch-flux
Open

fix(github-release): update flux group to v2.0.1 (patch)#64
renovate[bot] wants to merge 1 commit intomainfrom
renovate/patch-flux

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate bot commented May 13, 2023 •
edited
Loading

Mend Renovate logo banner

This PR contains the following updates:

Package Type Update Change
fluxcd/flux2 Kustomization patch v2.0.0-rc.1 -> v2.0.1
ghcr.io/fluxcd/flux-manifests patch v2.0.0-rc.1 -> v2.0.1

Release Notes

fluxcd/flux2 (fluxcd/flux2)

v2.0.1

Compare Source

Highlights

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

💡 For upgrading from Flux v0.x, please see the procedure documented in 2.0.0.

Fixes
  • Fix AWS auth for cross-region ECR repositories (source-controller, image-reflector-controller).
  • Prevent spurious alerts for skipped resources (kustomize-controller).
  • List removed resources for flux diff ks --kustomization-file (flux CLI).
  • Fix SLSA provenance generation for the Flux CLI binaries.
Components changelog
CLI Changelog
New Documentation

v2.0.0

Compare Source

Highlights

This is the first General Availability (GA) release of Flux v2.

Flux v2.0.0 comes with the promotion of the GitOps related APIs to v1 and adds horizontal scaling & sharding capabilities to Flux controllers. The Git bootstrap capabilities provided by the Flux CLI and by Flux Terraform Provider are now considered stable and production ready.

Starting with this version, the build, release and provenance portions of the Flux project supply chain provisionally meet SLSA Build Level 3.

Flux GA is fully integrated with Kubernetes Workload Identity for AWS, Azure and Google Cloud to facilitate passwordless authentication to OCI sources (container images, OCI artifacts, Helm charts).

The Flux alerting capabilities have been extended with PagerDuty and Google Pub/Sub support. The improved Alert v1beta2 API provides better control over events filtering and allows users to enrich the alerts with custom metadata.

Supported versions

Starting with this version, the Flux CLI and the GA components (source-controller, kustomize-controller and notification-controller) follow the release cadence and support pledge documented in the Flux release specification.

Kubernetes compatibility

This release is compatible with the following Kubernetes versions:

Kubernetes version Minimum required
v1.24 >= 1.24.0
v1.25 >= 1.25.0
v1.26 >= 1.26.0
v1.27 >= 1.27.1

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

Flux ecosystem support

The following (open-source) extensions & integrations are compatible with this Flux release, starting from the specified minimum version or higher.

Type Project Version
Flux Web UI weave-gitops 0.26.0
Terraform integration tf-controller 0.15.0
API changes
GitRepository v1

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:

  • the deprecated field .spec.gitImplementation was removed
  • the unused field .spec.accessFrom was removed
  • the deprecated field .status.contentConfigChecksum was removed
  • the deprecated field .status.artifact.checksum was removed
  • the .status.url was removed (replaced by .status.artifact.url)
Kustomization v1

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:

  • the deprecated field .spec.validation was removed
  • the deprecated field .spec.patchesStrategicMerge was removed (replaced by .spec.patches)
  • the deprecated field .spec.patchesJson6902 was removed (replaced by .spec.patches)
Receiver v1

The Receiver 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:

  • the deprecated field .status.url was removed (replaced by .status.webhookPath)
Upgrade procedure

Upgrade Flux from v0.x to v2.0.0 either by rerunning bootstrap or by using the Flux GitHub Action.

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

  1. Remove the deprecated fields from the GitRepository and Kustomization definitions.
  2. Commit, push and reconcile the fields removal changes.
  3. Set apiVersion: source.toolkit.fluxcd.io/v1 in the YAML files that contain GitRepository definitions.
  4. Set apiVersion: kustomize.toolkit.fluxcd.io/v1 in the YAML files that contain Flux Kustomization definitions.
  5. Set apiVersion: notification.toolkit.fluxcd.io/v1 in the YAML files that contain Receiver definitions.
  6. Update the API version of GitRepository and Kustomization objects present in the .spec.resources list of Receiver definitions.
  7. 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 beta versions will be removed after 6 months.

New Documentation

❤️ Big thanks to all the Flux contributors that helped us reach this milestone!
👏 And a special shoutout to the Flux community who supported us over the years!

Components changelog
CLI Changelog

v2.0.0-rc.5

Compare Source

Highlights

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.

💡 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.

Fixes and improvements
  • Fix support for Git v2 servers.
  • Suppress misleading error message [controller-runtime] log.SetLogger(...) was never called... (CLI).
  • Include both revision and token in event metadata, if present (helm-controller).
  • Update source-controller to patch a vulnerability in Sigstore (CVE-2023-33199)

Components Changelog

CLI Changelog

v2.0.0-rc.4

Compare Source

Highlights

This 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.

💡 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.

Fixes and improvements
  • Full support for Azure Workload Identity when connecting Flux to Azure Container Registry, Azure Blog Storage and Azure Key Vault.
  • New command flux reconcile source chart for pulling Helm OCI charts on-demand from container registries (CLI).
  • Retry OCI operations on network errors for flux push artifact (CLI).
  • Support annotated Git tags with .spec.ref.name in GitRepository (source-controller).
  • Fix pulling Helm OCI charts from ACR when using Azure OIDC (source-controller).
  • Fix incorrect rate limiting for HelmRelease events (notification-controller).
  • All components have been updated to patch vulnerabilities in Docker (CVE-2023-28840, CVE-2023-28841, CVE-2023-28842) and Sigstore (CVE-2023-30551).

Components changelog

CLI Changelog

v2.0.0-rc.3

Compare Source

Highlights

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.

💡 For upgrading from v0.x, please see the procedure documented in RC.1.

⚠️ 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.

Fixes and improvements
  • Fix bootstrap on GKE (RC.2 regression due to insufficient quota for critical pods).
  • All controller base images have been updated to Alpine 3.18.
  • All components have been updated to patch CVE-2023-2253 and CVE-2023-1732 (note that Flux is not affected, these CVEs are for packages used in tests).
  • Verify artifacts integrity, issue warning events and remove tempered artifacts from storage forcing a re-download (source-controller).
  • Files with executable permissions are now archived with their mode set to 0o744, allowing CI system to run them (source-controller).
  • The 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).
  • Improve the detection of values changes for HelmReleases by stable sorting them by key (helm-controller).

Components changelog

CLI Changelog

v2.0.0-rc.2

Compare Source

Highlights

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.

💡 For upgrading from v0.x, please see the procedure documented in RC.1.

⚠️ 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.

Fixes and improvements
  • Fix bootstrap for BitBucket Server (CLI).
  • Fix secrets decryption when using Azure Key Vault (kustomize-controller).
  • Fix drift detection for renamed HelmReleases (helm-controller).
  • Improve performance when handling webhook receivers (notification-controller).
  • The Alert v1beta2 API has a new optional field .spec.inclusionList for fine-grained control over events filtering (notification-controller).
  • The deprecated field .status.url was removed from the Receiver v1 API (notification-controller).
  • Add support for commit signing using OpenPGP keys with passphrases (image-automation-controller).

Components changelog

CLI Changelog

Configuration

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

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

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

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

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

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot changed the title fix(github-release): update fluxcd/flux2 to v2.0.0-rc.3 fix(github-release): update fluxcd/flux2 to v2.0.0-rc.4 May 29, 2023
@renovate renovate bot force-pushed the renovate/patch-flux branch from 2782d24 to c3339ca Compare May 29, 2023 12:57
@renovate renovate bot changed the title fix(github-release): update fluxcd/flux2 to v2.0.0-rc.4 fix(github-release): update flux group to v2.0.0-rc.5 (patch) Jun 2, 2023
@renovate renovate bot force-pushed the renovate/patch-flux branch from c3339ca to 45d0b92 Compare June 2, 2023 17:37
@renovate renovate bot changed the title fix(github-release): update flux group to v2.0.0-rc.5 (patch) fix(github-release): update flux group (patch) Jul 5, 2023
@renovate renovate bot force-pushed the renovate/patch-flux branch from 45d0b92 to b17dc6a Compare July 5, 2023 16:08
@renovate renovate bot changed the title fix(github-release): update flux group (patch) fix(github-release): update flux group to v2.0.0 (patch) Jul 5, 2023
@renovate renovate bot force-pushed the renovate/patch-flux branch from b17dc6a to 5009e3d Compare July 5, 2023 20:00
@renovate renovate bot changed the title fix(github-release): update flux group to v2.0.0 (patch) fix(github-release): update flux group to v2.0.1 (patch) Jul 11, 2023
@renovate renovate bot force-pushed the renovate/patch-flux branch from 5009e3d to fb58f71 Compare July 11, 2023 15:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

area/kubernetes renovate/github-release type/patch

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants