Mayastor User Reference
version/2.0
version/2.0
  • Welcome to Mayastor!
  • Scope
  • Basic Architecture
  • Quickstart
    • Prerequisites
    • Preparing the Cluster
    • Deploy Mayastor
    • Configure Mayastor
      • Storage Class Parameters
    • Deploy a Test Application
  • Advanced Operations
    • Mayastor Kubectl Plugin
    • High Availability
    • Supportability
    • Monitoring
    • Node Cordon
    • Node Drain
  • Additional Information
    • Upgrade
    • Tips and Tricks
    • Performance Tips
    • I/O Path Description
    • Replica Operations
    • Call-home metrics
    • Tested Third Party Software
  • Basic Troubleshooting
  • FAQs
  • Known Limitations
  • Known Issues
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. Advanced Operations

Node Cordon

PreviousMonitoringNextNode Drain

Last updated 10 months ago

Was this helpful?

This website/page will be End-of-life (EOL) after 31 August 2024. We recommend you to visit for the latest Mayastor documentation (v2.6 and above).

Mayastor is now also referred to as OpenEBS Replicated PV Mayastor.

Cordoning a node marks or taints the node as unschedulable. This prevents the scheduler from deploying new resources on that node. However, the resources that were deployed prior to cordoning off the node will remain intact.

This feature is in line with the node-cordon functionality of Kubernetes.

To add a label and cordon a node, execute:

kubectl-mayastor cordon node <node_name> <label>

To get the list of cordoned nodes, execute:

kubectl-mayastor get cordon nodes

To view the labels associated with a cordoned node, execute:

kubectl-mayastor get cordon node <node_name>

How to uncordon a node?

In order to make a node schedulable again, execute:

kubectl-mayastor uncordon node <node_name> <label>

</div>
The above command allows the Kubernetes scheduler to deploy resources on the node.
OpenEBS Documentation