fix(container): update flux operator group ( 0.58.0 ➔ 0.58.1 ) #2017
No reviewers
Labels
No labels
area/bootstrap
area/ci
area/kubernetes
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
renovate/container
renovate/github-action
renovate/github-release
renovate/grafana-dashboard
renovate/helm
renovate/terraform
type/digest
type/major
type/minor
type/patch
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
GiorgioAresu/home-ops!2017
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/flux-operator"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
0.58.0→0.58.10.58.0→0.58.1Release Notes
controlplaneio-fluxcd/flux-operator (ghcr.io/controlplaneio-fluxcd/charts/flux-instance)
v0.58.1Compare Source
What's Changed
distro mirrorcommand by @stefanprodan in #998inventory.Diffwith map lookup by @manoj-1407 in #981golang.org/xpackages by @stefanprodan in #999New Contributors
Full Changelog: https://github.com/controlplaneio-fluxcd/flux-operator/compare/v0.58.0...v0.58.1
Configuration
📅 Schedule: (in timezone Europe/Rome)
🚦 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 these updates again.
This PR has been generated by Mend Renovate CLI.
konflate — summary
✅ No rendered changes.
View the full rendered diff →
konflate · rendered
4f492ec· advisory, not a gate⚠️ Automated recommendation: REQUEST CHANGES
Analysis engine: minimax/MiniMax-M2-7-anthropic@http://litellm.ai.svc.cluster.local:4000/v1 (anthropic)
Recommendation: Request Changes
This patch update bumps
flux-operatorandflux-instanceHelm charts from0.58.0to0.58.1in the bootstrap helmfile. However, the repository impact scan reveals that the same version0.58.0is still referenced in two OCIRepository resources underkubernetes/apps/flux-system/.Changes Made
kubernetes/bootstrap/helmfile.d/01-apps.yaml: Updated two HelmRelease chart versions (flux-operator,flux-instance) from0.58.0→0.58.1Issue Found
The PR updates the bootstrap HelmReleases but misses updating the OCIRepository tags that source the flux-operator manifests:
kubernetes/apps/flux-system/flux-instance/app/ocirepository.yaml:13→tag: 0.58.0(still)kubernetes/apps/flux-system/flux-operator/app/ocirepository.yaml:13→tag: 0.58.0(still)Additionally,
flux-instance/helmrelease.yamlreferences artifactoci://ghcr.io/controlplaneio-fluxcd/flux-operator-manifests:v0.58.0.This creates a version mismatch: the bootstrap will install
flux-operatorv0.58.1, but the flux-system apps will continue syncing from the v0.58.0 manifests — potentially causing the operator to manage manifests at a different version than what it was bootstrapped with.Action Required
Update the
tag:fields in the twoocirepository.yamlfiles and theartifact:reference influx-instance/helmrelease.yamlto0.58.1as well, so all flux-operator references are consistent.Sources
0.58.0still referenced in 3 flux-system app fileskubernetes/bootstrap/helmfile.d/01-apps.yamlchangedStandards Compliance