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

Retry upgrade without changing the helmrelease #297

Closed
Jeinhaus opened this issue Jul 12, 2021 · 0 comments · Fixed by #823
Closed

Retry upgrade without changing the helmrelease #297

Jeinhaus opened this issue Jul 12, 2021 · 0 comments · Fixed by #823

Comments

@Jeinhaus
Copy link

What is currently your suggested action to take when I need to retry a helmrelease's upgrade without the need to change anything.
Assume the upgrade fails because the container registry hosting the image is down at the time when the helmrelease is upgraded.
If we configured retries and remediations we will probably end in a state where the helmrelease's Status will show upgrade retries exhausted.
If I then know, that the registry is back up again, how do you suggest to retry the upgrade again?
Currently using flux suspend...&& flux resume ... works but seems kind of strange.
Is there any other way I am not aware of?
Might be related to #268 and #186

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