Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update dependency fluxcd/flux2 to v0.41.2 [ci-skip] #1

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update dependency fluxcd/flux2 to v0.41.2 [ci-skip] #1

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 28, 2022 •
edited
Loading

This PR contains the following updates:

Package Update Change
fluxcd/flux2 minor v0.29.3 -> v0.41.2

Release Notes

fluxcd/flux2 (fluxcd/flux2)

v0.41.2

Compare Source

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.

💡 For more information about other features introduced in v0.41.0, please refer to the changelog for this version.

Components Changelog
CLI Changelog

v0.41.1

Compare Source

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

💡 For more information about other features introduced in v0.41.0, please refer to the changelog for this version.

Components changelog
CLI Changelog

v0.41.0

Compare Source

Flux v0.41.0 comes with new features and improvements. Users are encouraged to upgrade for the best experience.

Features and improvements
  • Experimental support of drift detection of Helm releases compared to cluster-state.
  • Improved handling of 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.
  • Opt-in OOM watcher in helm-controller to handle graceful termination of the controller before it is forcefully killed by Kubernetes' OOM killer.
  • Kubernetes client and Custom Resource Definition life-cycle improvements to reduce the memory consumption of the helm-controller, with observed reductions up to 50%.
  • Opt-in allowance of DNS lookups during the rendering of Helm templates in the helm-controller via feature gate.
  • Optional disabling of the cache of the status poller used to determine the health of the resources applied by the kustomize-controller. This may improve memory usage on large scale clusters at the cost of more direct API calls.
  • Changes to the logging of all controllers to ensure Kubernetes components like the discovery client use the configured logging format.
  • New flux events command to display Kubernetes events for Flux resources, including the events of a referenced resource.
  • Custom annotations can now be set with flux push using --annotations.
New documentation
Components changelog
CLI Changelog

v0.40.2

Compare Source

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

⚠️ Note that v0.40.0 contained breaking changes, please refer to the changelog for more information.

Components changelog
CLI Changelog

v0.40.1

Compare Source

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.

⚠️ Note that v0.40.0 contained breaking changes, please refer to the changelog for more information.

Components changelog
CLI Changelog

v0.40.0

Compare Source

Highlights

Flux v0.40.0 comes with new features and improvements. Users are encouraged to upgrade for the best experience.

Breaking changes

Image Automation

The image-reflector-controller autologin flags have been deprecated and are no longer used.
Please see the new API specification and migration instructions in the controller changelog.

Notifications

The source revision format reported by the Flux controllers has changed according to RFC-0005.
The events referring to Git repositories, will report the revision in the format <branch|tag>@&#8203;sha1:<commit> instead of <branch|tag>/<commit>.
For more details please see the source-controller changelog.

OCI artifacts

The OCI artifacts produced with flux push artifact have now custom media types:

  • artifact media type application/vnd.oci.image.manifest.v1+json
  • config media type application/vnd.cncf.flux.config.v1+json
  • content media type application/vnd.cncf.flux.content.v1.tar+gzip
Features and improvements
  • The GitRepository API has a new optional field .spec.ref.name for specifying a Git Reference.
    This allows Flux to reconcile resources from GitHub Pull Requests (refs/pull/<id>/head) and GitLab Merge Requests (refs/merge-requests/<id>/head).
  • The ImageRepository and ImagePolicy APIs have been promoted to v1beta2.
  • Allow specifying the cloud provider contextual login for container registries with ImageRepository.spec.provider.
  • Improve observability of ImageRepository by showing the latest scanned tags under .status.lastScanResult.latestTags.
  • Improve observability of ImagePolicy by reporting the current and previous image tag in status and events.
  • The Kubernetes builtin cluster roles: view, edit and admin have been extended to allow access to Flux custom resources.
  • Print a report of Flux custom resources and the amount of cumulative storage used for each source type with flux stats -A.
New Documentation
Components changelog
CLI Changelog

v0.39.0

Compare Source

Highlights

Flux v0.39.0 comes with new features and improvements. Users are encouraged to upgrade for the best experience.

Starting with this version, the Flux controllers come with SBOMs and SLSA Provenance Attestations embedded in their container images.

The Flux Terraform Provider has a new resource for bootstrapping Flux, without depending on third-party Terraform providers, that allows customising the controllers at install time. Users are encouraged to migrate to this new resources and provide feedback.

The Flux CLI is now included in Wolfi OS, the Linux (Un)distro designed for securing the software supply chain. The Chainguard team and Wolfi maintainers are shipping updates for the Flux package on a regular basis.

Features and improvements
  • Recreate immutable resources (e.g. Kubernetes Jobs) by annotating or labeling them with kustomize.toolkit.fluxcd.io/force: enabled.
  • Support for HTTPS bearer token authentication for Git repositories.
  • Improve memory usage by disabling the caching of Secret and ConfigMap resources in all controllers.
  • Better observability with progressive status updates for Sources (Git, OCI, Helm, S3 Buckets).
  • Allow extracting the OCI artifact SHA256 digest for Cosign with flux push artifact -o json.
  • Track CRDs managed by Flux, flux trace and flux tree will show which HelmRelease deployed which CRDs.
  • Allow the Flux GitHub Action to use a GitHub token when checking for updates to avoid rate limiting.
New documentation
Components changelog
CLI Changelog

v0.38.3

Compare Source

Highlights

Flux v0.38.3 is a patch release that comes with fixes and small improvements to the CLI.
Users are encouraged to upgrade for the best experience.

CLI Changelog

v0.38.2

Compare Source

Flux v0.38.2 is a patch release that comes with fixes for the Notification API v1beta1 to v1beta2 upgrade.
In addition, this release improves the handling of the graceful shutdown for helm-controller.
Users are encouraged to update Flux directly to v0.38.2 for the best experience.

Components changelog
CLI Changelog

v0.38.1

Compare Source

Flux v0.38.1 is a patch release that comes with fixes for the Notification API v1beta1 to v1beta2 upgrade.
Users are encouraged to update Flux directly to v0.38.1 for the best experience.

Changelog

v0.38.0

Compare Source

Highlights

Flux v0.38.0 comes with new features and improvements. Users are encouraged to upgrade for the best experience.

Notification API v1beta2

This release graduates the Notification APIs to v1beta2. After upgrading the controllers on your clusters, you need to update the notification Custom Resources in Git by replacing notification.toolkit.fluxcd.io/v1beta1 with notification.toolkit.fluxcd.io/v1beta2 in all YAML manifests.

Breaking changes
  • The Alert.spec.summary has a max length of 255 characters.
  • The Provider.spec.address and Provider.spec.proxy have a max length of 2048 characters.
  • The Receiver.status.url was deprecated in favour of Receiver.status.webhookPath.

For more details about v1beta2 please see the notification-controller chagelog and the API spec documentation.

Features and improvements
  • Support for defining Kustomize components with Kustomization.spec.components.
  • Support for piping multi-doc YAMLs when publishing OCI artifacts with kustomize build . | flux push artifact --path=-.
  • Support for Gitea commit status updates with Provider.spec.type set to gitea.
  • Improve the memory usage of helm-controller by disabling the caching of Secret and ConfigMap resources.
  • Update the Helm SDK to v3.10.3 (fix for Helm CVEs).
  • All code references to libgit2 were removed, and the GitRepository.spec.gitImplementation field is no longer being honored.
Documentation improvements

The official example repository was refactored. The new version comes with the following improvements:

  • Make the example compatible with ARM64 Kubernetes clusters.
  • Add Weave GitOps Helm release to showcase the Flux UI.
  • Replace the ingress-nginx Bitnami chart with the official one that contains multi-arch container images.
  • Add cert-manager Helm release to showcase how to install CRDs and custom resources using dependsOn.
  • Add Let's Encrypt ClusterIssuer to showcase how to patch resources in production with Flux Kustomization.
  • Add the flux-system overlay to showcase how to configure Flux at bootstrap time.
Components changelog
CLI Changelog

v0.37.0

Compare Source

Highlights

Flux v0.37.0 comes with new features and improvements. Users are encouraged to upgrade for the best experience.

Breaking changes
Deprecation of gitImplementation

The interpretation of the gitImplementation field of GitRepository by source-controller and image-automation-controller has been deprecated, and will effectively always use go-git. This now supports all Git servers, including Azure DevOps and AWS CodeCommit, which previously were only supported by libgit2.

To opt-out from this behaviour, and get the controller to honour the field .spec.gitImplementation, start the controller with: --feature-gates=ForceGoGitImplementation=false.

For more information on this change, refer to the controllers's respective changelogs listed below.

Automatic force-push of ImageUpdateAutomation

Starting from this version, ImageUpdateAutomation objects with a .spec.PushBranch specified will have the push branch refreshed automatically via force push. To opt-out from this behaviour, start the controller with: --feature-gates=GitForcePushBranch=false.

Features and improvements
  • Support for bootstrapping Azure DevOps and AWS CodeCommit repositories using flux bootstrap git.
  • Support cloning of Git v2 protocol (Azure DevOps and AWS CodeCommit) for go-git Git provider.
  • Support force-pushing ImageUpdateAutomation repositories.
  • Allow a dry-run of flux build kustomization with --dry-run and --kustomization-file ./path/to/local/my-app.yaml. Using these flags, variable substitutions from Secrets and ConfigMaps are skipped, and no connection to the cluster is made.
  • Use signed OCI Helm chart for kube-prometheus-stack.
New documentation

Components changelog

CLI Changelog

v0.36.0

Compare Source

Highlights

Flux v0.36.0 comes with new features and improvements. Users are encouraged to upgrade for the best experience.

Features and improvements
  • Verify OCI Helm charts signed by Cosign (including keyless) with HelmChart.spec.verify.
  • Allow publishing a single YAML file to OCI with flux push artifact <URL> --path=deploy/install.yaml.
  • Detect changes to local files before pushing to OCI with flux diff artifact <URL> --path=<local files>.
  • New Alert Provider type named generic-hmac for authenticating the webhook requests coming from notification-controller.
  • The Kustomization.status.conditions have been aligned with Kubernetes standard conditions and kstatus.
  • The kustomize-controller memory usage was reduced by 90% when performing artifact operations.
New documentation

Components changelog

CLI Changelog

v0.35.0

Compare Source

Highlights

Flux v0.35.0 comes with new features and improvements. Users are encouraged to upgrade for the best experience.

Breaking changes

Strict validation rules have been put in place for API fields which define a time duration, such as .spec.interval. Effectively, this means values without a time unit (e.g. ms, s, m, h) will now be rejected by the API server.

Features and improvements
  • Verify OCI artifacts signed by Cosign (including keyless) with OCIRepository.spec.verify.
  • Allow pulling Helm charts dependencies from HTTPS repositories with mixed self-signed TLS and public CAs.
  • Allow pulling Helm charts from OCI artifacts stored at the root of AWS ECR.
  • Allow running bootstrap for insecure HTTP Git servers with flux bootstrap git --allow-insecure-http --token-auth.
  • Improve health checking for global objects such as ClusterClass, GatewayClass, StorageClass, etc.
  • The controllers and the Flux CLI are now built with Go 1.19.

For more information on OCI and Cosign support please see the Flux documentation.

Components changelog

CLI Changelog

v0.34.0

Compare Source

Highlights

Flux v0.34.0 comes with new features and improvements. Users are encouraged to upgrade for the best experience.

Breaking changes

The Flux controller logs have been aligned with the Kubernetes structured logging.
For more details on the new logging structure please see: fluxcd/flux2#3051.

Features and improvements
  • OCIRepository.spec.insecure Allow pulling artifacts from an in-cluster Docker Registry over plain HTTP.
  • Allow defining OCI sources for non-TLS container registries with flux create source oci --insecure.
  • Enable contextual login when publishing OCI artifacts from a Cloud VM using flux push artifact --provider=aws|azure|gcp.
  • Prioritise static credentials over OIDC providers when pulling OCI artifacts from container registries on multi-tenant cluster.
  • Reconcile Kubernetes Class types (ClusterClass, GatewayClass, StorageClass, etc) in a dedicated stage before any other custom resources like Clusters, Gateways, Volumes, etc.
  • When multiple SOPS providers are available, run the offline decryption methods first to avoid failures due to KMS unavailability.
  • Add finalizers to the notification API to properly record the reconciliation metrics for deleted resources.
  • Publish the Flux install manifests as OCI artifacts on GitHub and DockerHub container registries under fluxcd/flux-manifests.

Components Changelog

CLI Changelog

v0.33.0

Compare Source

Highlights

Flux v0.33.0 comes with new features and improvements. Users are encouraged to upgrade for the best experience.

Features and improvements
  • HelmRepository.spec.provider Enable contextual login to container registries when pulling Helm charts from Amazon Elastic Container Registry, Azure Container Registry and Google Artifact Registry.
  • OCIRepository.spec.layerSelector Select which layer contains the Kubernetes configs by specifying a matching OCI media type.
  • Bucket.spec.secretRef Authenticate to Azure Blob storage using SAS tokens.
  • Allow filtering OCI artifacts by semver and regex when listing artifact with flux list artifacts.
  • Allow excluding local files and directories when building and publishing artifacts with flux push artifact.
  • Mitigate denial-of-service on multi-tenant clusters by automatically recovering from panics encountered during reconciliation.
  • Update controllers to Kubernetes v1.25.0, Kustomize v4.5.7 and Helm v3.9.4.
New documentation

Components changelog

CLI Changelog

  • PR [#​3049](ht

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 this update again.

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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/fluxcd-flux2-0.x branch from 23565cc to 021b51c Compare June 29, 2022 17:17
@renovate renovate bot changed the title Update dependency fluxcd/flux2 to v0.31.2 [ci-skip] Update dependency fluxcd/flux2 to v0.31.3 [ci-skip] Jun 29, 2022
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-0.x branch from 021b51c to 62513e6 Compare July 18, 2022 14:29
@renovate renovate bot changed the title Update dependency fluxcd/flux2 to v0.31.3 [ci-skip] Update dependency fluxcd/flux2 to v0.31.4 [ci-skip] Jul 18, 2022
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-0.x branch from 62513e6 to d825f2c Compare July 27, 2022 19:26
@renovate renovate bot changed the title Update dependency fluxcd/flux2 to v0.31.4 [ci-skip] Update dependency fluxcd/flux2 to v0.31.5 [ci-skip] Jul 27, 2022
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-0.x branch from d825f2c to e0d033a Compare August 11, 2022 17:14
@renovate renovate bot changed the title Update dependency fluxcd/flux2 to v0.31.5 [ci-skip] Update dependency fluxcd/flux2 to v0.32.0 [ci-skip] Aug 11, 2022
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-0.x branch from e0d033a to afda749 Compare August 29, 2022 17:41
@renovate renovate bot changed the title Update dependency fluxcd/flux2 to v0.32.0 [ci-skip] Update dependency fluxcd/flux2 to v0.33.0 [ci-skip] Aug 29, 2022
@renovate renovate bot changed the title Update dependency fluxcd/flux2 to v0.33.0 [ci-skip] Update dependency fluxcd/flux2 to v0.32.0 [ci-skip] Sep 12, 2022
@renovate renovate bot changed the title Update dependency fluxcd/flux2 to v0.32.0 [ci-skip] Update dependency fluxcd/flux2 to v0.34.0 [ci-skip] Sep 12, 2022
@renovate renovate bot changed the title Update dependency fluxcd/flux2 to v0.34.0 [ci-skip] Update dependency fluxcd/flux2 to v0.35.0 [ci-skip] Sep 29, 2022
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-0.x branch from 828ae70 to ea16e8b Compare October 24, 2022 12:09
@renovate renovate bot changed the title Update dependency fluxcd/flux2 to v0.35.0 [ci-skip] Update dependency fluxcd/flux2 to v0.36.0 [ci-skip] Oct 24, 2022
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-0.x branch from ea16e8b to 54200c9 Compare November 22, 2022 21:01
@renovate renovate bot changed the title Update dependency fluxcd/flux2 to v0.36.0 [ci-skip] Update dependency fluxcd/flux2 to v0.37.0 [ci-skip] Nov 22, 2022
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-0.x branch from 54200c9 to d80974b Compare December 21, 2022 13:59
@renovate renovate bot changed the title Update dependency fluxcd/flux2 to v0.37.0 [ci-skip] Update dependency fluxcd/flux2 to v0.38.0 [ci-skip] Dec 21, 2022
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-0.x branch from d80974b to 61d2e42 Compare December 21, 2022 17:15
@renovate renovate bot changed the title Update dependency fluxcd/flux2 to v0.38.0 [ci-skip] Update dependency fluxcd/flux2 to v0.38.1 [ci-skip] Dec 21, 2022
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-0.x branch from 61d2e42 to 6c48801 Compare December 22, 2022 16:11
@renovate renovate bot changed the title Update dependency fluxcd/flux2 to v0.38.1 [ci-skip] Update dependency fluxcd/flux2 to v0.38.2 [ci-skip] Dec 22, 2022
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-0.x branch from 6c48801 to 5405be4 Compare January 10, 2023 18:37
@renovate renovate bot changed the title Update dependency fluxcd/flux2 to v0.38.2 [ci-skip] Update dependency fluxcd/flux2 to v0.38.3 [ci-skip] Jan 10, 2023
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-0.x branch from 5405be4 to 81b3eb2 Compare February 2, 2023 20:05
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-0.x branch from 43f0ef3 to 5cee4a8 Compare February 28, 2023 18:17
@renovate renovate bot changed the title Update dependency fluxcd/flux2 to v0.40.1 [ci-skip] Update dependency fluxcd/flux2 to v0.40.2 [ci-skip] Feb 28, 2023
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-0.x branch from 5cee4a8 to aaf5038 Compare March 9, 2023 18:37
@renovate renovate bot changed the title Update dependency fluxcd/flux2 to v0.40.2 [ci-skip] Update dependency fluxcd/flux2 to v0.41.0 [ci-skip] Mar 9, 2023
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-0.x branch from aaf5038 to 853d5f4 Compare March 10, 2023 16:07
@renovate renovate bot changed the title Update dependency fluxcd/flux2 to v0.41.0 [ci-skip] Update dependency fluxcd/flux2 to v0.41.1 [ci-skip] Mar 10, 2023
@renovate renovate bot changed the title Update dependency fluxcd/flux2 to v0.41.1 [ci-skip] Update dependency fluxcd/flux2 to v0.41.2 [ci-skip] Mar 21, 2023
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-0.x branch 2 times, most recently from 5d00f35 to de18a4d Compare May 9, 2023 18:59
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-0.x branch from de18a4d to 1a2fe42 Compare June 7, 2023 07:31
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-0.x branch 2 times, most recently from 345a754 to 578cbba Compare June 17, 2023 06:05
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-0.x branch from 578cbba to 7e66cb5 Compare July 7, 2023 02:04
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-0.x branch from 7e66cb5 to f3ebb92 Compare July 17, 2023 17:17
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-0.x branch from f3ebb92 to e7a6e93 Compare August 18, 2023 08:28
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-0.x branch 2 times, most recently from 3f82047 to d3baa0e Compare September 7, 2023 22:28
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-0.x branch from bc5c26d to 3b44b63 Compare December 17, 2023 22:22
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-0.x branch 3 times, most recently from d9b7764 to 17ddf09 Compare January 19, 2024 07:31
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-0.x branch from 17ddf09 to 8f72d93 Compare February 27, 2024 00:59
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-0.x branch from 8f72d93 to a94dc27 Compare April 23, 2024 04:29
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-0.x branch from a94dc27 to c72f3fa Compare June 9, 2024 20:25
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-0.x branch from c72f3fa to 2ec084e Compare July 30, 2024 03:08
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-0.x branch from f73edcd to 9599ace Compare November 11, 2024 02:39
@renovate renovate bot force-pushed the renovate/fluxcd-flux2-0.x branch from 9599ace to 061755e Compare November 22, 2024 01:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@nshores nshores

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@nshores