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.

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

fix(github-release): update fluxcd/flux2 to v2.0.0-rc.3 #715

Merged
merged 1 commit into from
May 17, 2023

Conversation

snoopy82481-bot[bot]
Copy link
Contributor

@snoopy82481-bot snoopy82481-bot bot commented May 9, 2023

This PR contains the following updates:

Package Type Update Change
fluxcd/flux2 Kustomization patch v2.0.0-rc.1 -> v2.0.0-rc.3

Release Notes

fluxcd/flux2

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 - 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 has been generated by Renovate Bot.

@snoopy82481-bot snoopy82481-bot bot requested a review from snoopy82481 as a code owner May 9, 2023 17:12
@snoopy82481-bot snoopy82481-bot bot added renovate/github-release type/patch size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels May 9, 2023
@snoopy82481-bot
Copy link
Contributor Author

snoopy82481-bot bot commented May 9, 2023

🦙 MegaLinter status: ✅ SUCCESS

Descriptor Linter Files Fixed Errors Elapsed time
✅ COPYPASTE jscpd yes no 1.14s
✅ REPOSITORY git_diff yes no 0.02s
✅ REPOSITORY secretlint yes no 1.66s
✅ YAML prettier 1 0 0.39s
✅ YAML yamllint 1 0 0.22s

See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

MegaLinter is graciously provided by OX Security

| datasource  | package      | from        | to          |
| ----------- | ------------ | ----------- | ----------- |
| github-tags | fluxcd/flux2 | v2.0.0-rc.1 | v2.0.0-rc.3 |
@snoopy82481-bot snoopy82481-bot bot changed the title fix(github-release): update fluxcd/flux2 to v2.0.0-rc.2 fix(github-release): update fluxcd/flux2 to v2.0.0-rc.3 May 12, 2023
@snoopy82481-bot snoopy82481-bot bot force-pushed the renovate/fluxcd-flux2-2.x branch from 42e074c to 3c7f1c5 Compare May 12, 2023 13:15
@snoopy82481 snoopy82481 merged commit 45a0eb2 into main May 17, 2023
@snoopy82481 snoopy82481 deleted the renovate/fluxcd-flux2-2.x branch May 17, 2023 17:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
renovate/github-release size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. type/patch
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant