Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unsuspend Helmrelease results in unnecesary upgrades #739

Closed
1 task done
athan88 opened this issue Jul 19, 2023 · 0 comments · Fixed by #738
Closed
1 task done

Unsuspend Helmrelease results in unnecesary upgrades #739

athan88 opened this issue Jul 19, 2023 · 0 comments · Fixed by #738

Comments

@athan88
Copy link

athan88 commented Jul 19, 2023

Describe the bug

We would like to use providers and alerts to notify us when a helmrelease gets upgraded. In our CI/CD process we suspend a helmrelease, and resume it after a while. Flux resume results in unnecessary helm upgrades, that notify us even when the release wasn't upgraded.

Steps to reproduce

  1. Suspend Helmrelease
  2. Resume Helmrelease
  3. Helmrelease attempts (sometimes multiple) upgrades even when no new versions are available on repository

Expected behavior

Helm release doesn't attempt an upgrade unless a new revision is available.

Screenshots and recordings

No response

OS / Distro

N/A

Flux version

v0.40.0

Flux check

► checking prerequisites
✗ flux 0.40.0 <2.0.1 (new version is available, please upgrade)
✔ Kubernetes 1.26.1 >=1.20.6-0
► checking controllers
✔ helm-controller: deployment ready
ghcr.io/fluxcd/helm-controller:v0.30.0
✔ image-automation-controller: deployment ready
ghcr.io/fluxcd/image-automation-controller:v0.30.0
✔ image-reflector-controller: deployment ready
ghcr.io/fluxcd/image-reflector-controller:v0.25.0
✔ kustomize-controller: deployment ready
ghcr.io/fluxcd/kustomize-controller:v0.34.0
✔ notification-controller: deployment ready
ghcr.io/fluxcd/notification-controller:v0.32.0
✔ source-controller: deployment ready
ghcr.io/fluxcd/source-controller:v0.35.1
► checking crds
alerts.notification.toolkit.fluxcd.io/v1beta2
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
imagepolicies.image.toolkit.fluxcd.io/v1beta2
imagerepositories.image.toolkit.fluxcd.io/v1beta2
imageupdateautomations.image.toolkit.fluxcd.io/v1beta1
kustomizations.kustomize.toolkit.fluxcd.io/v1beta2
ocirepositories.source.toolkit.fluxcd.io/v1beta2
providers.notification.toolkit.fluxcd.io/v1beta2
receivers.notification.toolkit.fluxcd.io/v1beta2
✔ all checks passed

Git provider

Bitbucket

Container Registry provider

Harbor

Additional context

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@stefanprodan stefanprodan transferred this issue from fluxcd/flux2 Jul 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant