Skip to content
This repository has been archived by the owner on Mar 3, 2022. It is now read-only.

How do I drain the node of Jiva Pods without causing read-only issues. #570

Open
kmova opened this issue Mar 30, 2019 · 0 comments
Open
Assignees

Comments

@kmova
Copy link
Contributor

kmova commented Mar 30, 2019

I have more than 5 nodes in the cluster. I am using the Jiva with default settings. I am willing to use ReplicaNodeSelector.

Can I have the procedure for the following cases:

  • I now want to bring down a node for maintenance. What is the best way to drain the node of the storage pods (especially replica pods) so that they don't get rescheduled.
  • Also, in case the node is not going to come back, how can I move these offline replica storage pods to a completely new node.
@kmova kmova self-assigned this Mar 30, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant