[feature-1435]: Disable Resiliency for Array Upgrades #1268
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
atye
requested review from
gallacher,
mjsdell,
prablr79,
rajkumar-palani,
AronAtDell and
sharmilarama
as code owners
alikdell
approved these changes
Oct 2, 2024
shaynafinocchiaro
approved these changes
Oct 2, 2024
adarsh-dell
approved these changes
Oct 3, 2024
sharmilarama
reviewed
Oct 4, 2024
| @@ -189,6 +189,9 @@ Similarly, the label selector for csi-powerscale, csi-unity, csi-powerstore and | |||
|
|
|||
| 3. As noted previously in the Limitations and Exclusions section, CSM for Resiliency has not yet been verified to work with ReadWriteMany or ReadOnlyMany volumes. Also, it has not been verified to work with pod controllers other than StatefulSet. | |||
|
|
|||
| ### Storage Array Upgrades | |||
| To avoid application pods getting stuck in a Pending state, CSM for Resiliency should be disabled for storage array upgrades; even if the storage array upgrade is advertised as non-distruptive. If the container orchestrator platform nodes lose connectivity with the array, which is more likely during an upgrade, then Resiliency will delete the application pods on the affected nodes and attempt to move them to a healthy node. If all of the nodes are affected, then the application pods will be stuck in a Pending state. | |||
There was a problem hiding this comment.
Is there another place where we could also reference this as a prerequisite? Chances are it will not be noticed in this page, it needs to be a reminder before any storage upgrade.
There was a problem hiding this comment.
This section is now added to the Deployment documentation for Helm and Operator as Prerequisite.
atye
force-pushed
the
usr/atye/resiliency-array-upgrade
branch
from
22bbd4d to
f960c3b
Compare
atye
force-pushed
the
usr/atye/resiliency-array-upgrade
branch
from
f960c3b to
8e7c0bf
Compare
gallacher
approved these changes
Oct 7, 2024
atye
force-pushed
the
usr/atye/resiliency-array-upgrade
branch
from
8e7c0bf to
eba7f43
Compare
coulof
pushed a commit
that referenced
this pull request
Oct 21, 2024
* storage array upgrades * add prerequisites to helm and note array upgrades in deployment docs
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.
Description
Add a section in Resiliency that it should be disabled for storage array upgrades.
GitHub Issues
List the GitHub issues impacted by this PR:
Checklist: