This repository has been archived by the owner on Jan 28, 2023. It is now read-only.
chore(deps): update dependency fluxcd/flux2 to v0.38.3 #724
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:
v0.36.0
->v0.38.3
⚠ Dependency Lookup Warnings ⚠
Warnings were logged while processing this repo. Please check the Dependency Dashboard for more information.
Release Notes
fluxcd/flux2
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
tov1beta2
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
tov1beta2
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 replacingnotification.toolkit.fluxcd.io/v1beta1
withnotification.toolkit.fluxcd.io/v1beta2
in all YAML manifests.Breaking changes
Alert.spec.summary
has a max length of 255 characters.Provider.spec.address
andProvider.spec.proxy
have a max length of 2048 characters.Receiver.status.url
was deprecated in favour ofReceiver.status.webhookPath
.For more details about
v1beta2
please see the notification-controller chagelog and the API spec documentation.Features and improvements
Kustomization.spec.components
.kustomize build . | flux push artifact --path=-
.Provider.spec.type
set togitea
.libgit2
were removed, and theGitRepository.spec.gitImplementation
field is no longer being honored.Documentation improvements
The official example repository was refactored. The new version comes with the following improvements:
ingress-nginx
Bitnami chart with the official one that contains multi-arch container images.cert-manager
Helm release to showcase how to install CRDs and custom resources usingdependsOn
.ClusterIssuer
to showcase how to patch resources in production with Flux Kustomization.flux-system
overlay to showcase how to configure Flux at bootstrap time.Components changelog
CLI Changelog
flux push
b6757d8
a8dd587
to1cc9026
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 ofGitRepository
by source-controller and image-automation-controller has been deprecated, and will effectively always usego-git
. This now supports all Git servers, including Azure DevOps and AWS CodeCommit, which previously were only supported bylibgit2
.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
flux bootstrap git
.go-git
Git provider.ImageUpdateAutomation
repositories.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.New documentation
Components changelog
CLI Changelog
fluxcd/pkg/git
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.
This PR has been generated by Mend Renovate. View repository job log here.