Storage Nodes

An operation against a single storage node is requested with a StorageNodeOps resource, which names the target StorageNode, carries the action, and is driven to completion by the Simplyblock Operator. Taking a worker out for maintenance needs no resource at all, since a cordon or a drain is picked up by the operator on its own.

Topic	Purpose
Storage Node Actions	The mechanism behind every operation: the target node, the request, the locking, the tracking.
Shutting Down a Storage Node	Stopping one node, and the conditions that refuse a graceful shutdown.
Restarting a Storage Node	Stopping and starting one node, optionally forced and reattaching its volumes.
Suspending a Storage Node	Stopping new volumes from being placed on a node that keeps running.
Resuming a Storage Node	Returning a suspended node to normal service.
Replacing a Storage Node	Choosing between a migration and a removal when hardware is replaced.
Migrating a Storage Node	Moving a storage node onto a different worker, keeping its identity and devices.
Removing a Storage Node	Draining the volumes off a storage node and taking it out of the cluster.
Coordinated Worker Node Drain	Protecting storage availability while a Kubernetes worker is cordoned or drained.