Releases: giantswarm/flux-app
Releases · giantswarm/flux-app
v0.24.0
v0.23.1
v0.23.0
Added
- Added the use the runtime/default seccomp profile.
- Added
clusterRoles.install
value that can disable installing theflux-view
andflux-edit
cluster roles. Enabled by default to install these resources.
Changed
- Use Cilium network policy when available for CRD installer
- Updated flux apps to v0.41.2
- Changed PSP to allow the same volumes as restricted, to prevent seccomp profile changes breaking pod creation.
v0.22.0
Added
- Added
PriorityClass
. - Added
CiliumNetworkPolicy
.
v0.21.2
Fixed
Fixed condition for internal upgrade.
Changed
- Control CPU limits and min allowed CPU + memory requests with VPA as well for flux controllers
v0.21.1
Release v0.21.1 (#176) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
v0.21.0
Release v0.21.0 (#174) Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
v0.20.2
Added
- Introduce interface for disabling feature gates.
v0.20.1
- Fixed quoting of pod template labels
v0.20.0
Added
- Add capability to attach custom labels and annotations to kustomize-contoller pod template
Changed
- Bump upstream flux toolkit version to from
v0.36.0
tov0.37.0
.- The interpretation of the
gitImplementation
field ofGitRepository
bysource-controller
andimage-automation-controller
has been deprecated, and will effectively always usego-git
. ImageUpdateAutomation
objects with a.spec.PushBranch
specified will have the push branch refreshed automatically via force push.ImagePolicy
CRD dropped versionv1alpha1
ImageRepository
CRD dropped versionv1alpha1
ImageUpdateAutomation
CRD dropped versionv1alpha1
- The interpretation of the
- Increased memory limits for CRD install job as it was observed to frequently get OOM killed