![]() this should reinstall/redeploy the “oci-monitor” component without disturbing the PX-OCI service or disrupting the storage, and the Kubernetes labels should work afterwards.Sometimes it may happen that Kubernetes labels processing stops altogether - in this case please reinstall the “oci-monitor” component by applying and then deleting the px/enabled=false label: kubectl label nodes -all px/enabled=false sleep 30 kubectl label nodes -all px/enabled.On a “busy cluster”, Kubernetes can take some time until it processes the node-labels change, and notifies Portowrx service – please allow a few minutes for labels to be processed.After you labeled a node with px/enabled=remove (or px/service=restart), and Portworx is not uninstalling (or, restarting):.Once the node is decommissioned, the drives can be replaced and recommissioned into the cluster. If there are multiple drive failures, a node can be decommissioned from the cluster. In this mode, you can replace up to one failed drive. If one of the Portworx nodes is in maintenance mode, this could be because one or more of the drives has failed.For example on centos, this will be yum install kernel-headers-`uname -r and yum install kernel-devel-`uname -r` To workaround this, install the kernel headers on the host. This can fail if the host sits behind a proxy. When the Portworx container boots on a node for the first time, it attempts to download kernel headers to compile it’s kernel module.Read here for more information about taints and tolerations. If one of your nodes has a custom taint, the Portworx pod will not get scheduled on that node unless you add a toleration in the Portworx DaemonSet spec.Without this, Portworx cluster nodes will not be able to communicate and cluster will be down. Ports 9001 - 9022 must be open for internal network traffic between nodes running Portworx.In an event of a disaster where, internal kvdb is in an unrecoverable error state follow this doc to recover your Portworx cluster.Portworx nodes cannot resolve kube-dns entries since Portworx containers are in the host network. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |