You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Flux check incorrectly reports "all checks passed" when testing newer clis with older flux installed distributions
Steps to reproduce
For instance, if your system is flux2 0.35.0, and you execute flux check with flux clis 2.x.x (up to 2.4.0) it passes all checks, but then "flux get all" does shows inconsistent resources (only helmrepos before 2.3.0, and nothing after)
Expected behavior
Maybe it's as simple as fluxcd 2.xx is a major breaking version from 0.x.x and they are just incompatible, but then does it make sense that fluxcd CLI 2.x.x says ok when flux checking against a 0.x.x cluster? At least there should be a message saying the CLI is incompatible with current installed version
Describe the bug
Flux check incorrectly reports "all checks passed" when testing newer clis with older flux installed distributions
Steps to reproduce
For instance, if your system is flux2 0.35.0, and you execute flux check with flux clis 2.x.x (up to 2.4.0) it passes all checks, but then "flux get all" does shows inconsistent resources (only helmrepos before 2.3.0, and nothing after)
Expected behavior
Maybe it's as simple as fluxcd 2.xx is a major breaking version from 0.x.x and they are just incompatible, but then does it make sense that fluxcd CLI 2.x.x says ok when flux checking against a 0.x.x cluster? At least there should be a message saying the CLI is incompatible with current installed version
Screenshots and recordings
No response
OS / Distro
amazoncorretto-21-alpine
Flux version
0.35.0
Flux check
With 2.4.0 over 0.35.0
► checking prerequisites
✔ Kubernetes 1.30.8... >=1.28.0-0
► checking version in cluster
✔ distribution: flux-v0.35.0
✔ bootstrapped: true
► checking controllers
✔ helm-controller: deployment ready
► ghcr.io/fluxcd/helm-controller:v0.25.0
✔ kustomize-controller: deployment ready
► ghcr.io/fluxcd/kustomize-controller:v0.29.0
✔ notification-controller: deployment ready
► ghcr.io/fluxcd/notification-controller:v0.27.0
✔ source-controller: deployment ready
► ghcr.io/fluxcd/source-controller:v0.30.0
► checking crds
✔ alerts.notification.toolkit.fluxcd.io/v1beta1
✔ buckets.source.toolkit.fluxcd.io/v1beta2
✔ gitrepositories.source.toolkit.fluxcd.io/v1beta2
✔ helmcharts.source.toolkit.fluxcd.io/v1beta2
✔ helmreleases.helm.toolkit.fluxcd.io/v2beta1
✔ helmrepositories.source.toolkit.fluxcd.io/v1beta2
✔ kustomizations.kustomize.toolkit.fluxcd.io/v1beta2
✔ ocirepositories.source.toolkit.fluxcd.io/v1beta2
✔ providers.notification.toolkit.fluxcd.io/v1beta1
✔ receivers.notification.toolkit.fluxcd.io/v1beta1
✔ all checks passed
Git provider
No response
Container Registry provider
No response
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: