fix(github-release): update flux group (patch) #90
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
🦙 MegaLinter status:
|
| Descriptor | Linter | Files | Fixed | Errors | Elapsed time |
|---|---|---|---|---|---|
| ✅ COPYPASTE | jscpd | yes | no | 1.43s | |
| ✅ REPOSITORY | git_diff | yes | no | 0.03s | |
| ✅ REPOSITORY | secretlint | yes | no | 1.87s | |
| prettier | 3 | 1 | 0.47s | ||
| ✅ YAML | yamllint | 3 | 0 | 0.24s |
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
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/patch-flux
branch
from
8cef5d3 to
4bd5244
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/patch-flux
branch
from
4bd5244 to
1ae2eac
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v2.0.0-rc.5->v2.0.1v2.0.0-rc.5->v2.0.12.0.45->2.0.46Release Notes
fluxcd/flux2 (fluxcd/flux2)
v2.0.1Compare Source
Highlights
Flux
v2.0.1is 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
source-controller,image-reflector-controller).kustomize-controller).flux diff ks --kustomization-file(fluxCLI).Components changelog
CLI Changelog
opensslandsha256sum$RUNNER_TOOL_CACHE, support MacOS and Windows, validate checksumNew Documentation
v2.0.0Compare 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:
v1.24>= 1.24.0v1.25>= 1.25.0v1.26>= 1.26.0v1.27>= 1.27.1Note 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.
0.26.00.15.0API 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:
.spec.gitImplementationwas removed.spec.accessFromwas removed.status.contentConfigChecksumwas removed.status.artifact.checksumwas removed.status.urlwas 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.commonMetadatawas 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:
.spec.validationwas removed.spec.patchesStrategicMergewas removed (replaced by.spec.patches).spec.patchesJson6902was 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:
.status.urlwas removed (replaced by.status.webhookPath)Upgrade procedure
Upgrade Flux from
v0.xtov2.0.0either 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:
GitRepositoryandKustomizationdefinitions.apiVersion: source.toolkit.fluxcd.io/v1in the YAML files that containGitRepositorydefinitions.apiVersion: kustomize.toolkit.fluxcd.io/v1in the YAML files that contain FluxKustomizationdefinitions.apiVersion: notification.toolkit.fluxcd.io/v1in the YAML files that containReceiverdefinitions.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
flux pushexample for ECRgo.modversion with Kubernetes (Go 1.20)flux logsmore lenientminiflux/v2 (ghcr.io/miniflux/miniflux)
v2.0.46Compare Source
golang.org/x/*dependencies andgo-oidcto v3.6.0go-httpbinto run tests locally and avoid remote calls tohttpbin.orgtotal_unreadandfeed_countpq: time zone displacement out of rangeerrorsenclosures_user_entry_url_idxConfiguration
📅 Schedule: Branch creation - "before 6am" in timezone America/Detroit, 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Mend Renovate. View repository job log here.