Force rollout from a failing state #14
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
marcelldls
force-pushed
the
rollout-from-failing
branch
from
1eb0e33 to
20d552b
Compare
|
Note to self after merge: update https://github.com/epics-containers/ec-services-template which is still on |
|
To be tested against adaravis |
|
Do you think this is OK to merge? I still keep seeing the issue this fixes. |
Sorry I have not been able to test this against hardware with visr being powered down - apparently we are back up as of last night so I will try get to this |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If the pods are in a failing state (maybe bad image version for example), then doing an
ec deployupdates the helm application but the pods do not update (kubernetes/kubernetes#67250)A suggested fix in the issue is to set
podManagementPolicy: Parallel- which I have successfully tested onec deployOne thing to note is that this update will require a manual delete and deploy as per kubernetes/kubernetes#117693