Hello. What is the procedure for moving KVDB processes from one set of nodes in k8s or OpenShift to another? The only thing I was able to achieve is to start etcd on the target set by adding -kvdb_cluster_size “5” parameter to portworx DaemonSet, but there doesn’t seem to be a way to stop it on the old nodes. One would think that labeling all target nodes with px/metadata-node=true and all old nodes with px/metadata-node=false label would simply shut etcd down on the latter, but no luck. Removing -kvdb_cluster_size, which effectively sets it to 3, didn’t help either. I’d like to know if there is a way to do this via portworx itself before resorting to removing etcd endpoints via etcdctl.
Related topics
Topic | Replies | Views | Activity | |
---|---|---|---|---|
Steps to move the ETCD database to specific or another disk within the same node | 0 | 1026 | March 27, 2021 | |
Kvdb node addition when using portworx operator | 0 | 639 | February 9, 2022 | |
Change Portworx Node Type / Node Pool Migration with zero downtime | 0 | 610 | February 23, 2021 | |
Fail to start Portworx | 1 | 1343 | May 26, 2021 | |
PX on self-managed k8s on GCP cloud | 2 | 534 | January 4, 2021 |