Skip to content

Latest commit

 

History

History
110 lines (85 loc) · 2.9 KB

user-manual.md

File metadata and controls

110 lines (85 loc) · 2.9 KB
Raw

User manual

This is the user manual for TopoLVM. For deployment, please read ../deploy/README.md.

Table of contents

StorageClass

An example StorageClass looks like this:

kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
  name: topolvm-provisioner
provisioner: topolvm.cybozu.com
parameters:
  "csi.storage.k8s.io/fstype": "xfs"
volumeBindingMode: WaitForFirstConsumer

provisioner must be topolvm.cybozu.com.

parameters are optional. To specify a filesystem type, give csi.storage.k8s.io/fstype parameter.

Supported filesystems are: ext4, xfs, and btrfs.

volumeBindingMode can be either WaitForFirstConsumer or Immediate. WaitForFirstConsumer is recommended because TopoLVM cannot schedule pods wisely if volumeBindingMode is Immediate.

Pod priority

Pods using TopoLVM should always be prioritized over other normal pods. This is because TopoLVM pods can only be scheduled to a single node where its volumes exist whereas normal pods can be run on any node.

To give TopoLVM pods high priority, first create a PriorityClass:

apiVersion: scheduling.k8s.io/v1
kind: PriorityClass
metadata:
  name: topolvm
value: 1000000
globalDefault: false
description: "Pods using TopoLVM volumes should use this class."

and specify that PriorityClass in priorityClassName field as follows:

apiVersion: v1
kind: Pod
metadata:
  name: test
spec:
  priorityClassName: topolvm
  containers:
  - name: test
    image: nginx
    volumeMounts:
    - mountPath: /test1
      name: my-volume
  volumes:
    - name: my-volume
      persistentVolumeClaim:
        claimName: topolvm-pvc

Node maintenance

Retiring nodes

To remove a node and volumes/pods on the node from the cluster, follow these steps:

  1. Run kubectl drain NODE --ignore-daemonsets=true. --ignore-daemonsets=true avoids topolvm-node deletion. If drain stacks due to PodDisruptionBudgets or something, try --force option.
  2. Run kubectl delete nodes NODE
  3. TopoLVM will remove Pods and PersistentVolumeClaims on the node.
  4. StatefulSet controller reschedules Pods and PVCs on other nodes.

Rebooting nodes

To reboot a node without removing volumes, follow these steps:

  1. Run kubectl drain NODE --ignore-daemonsets=true --ignore-daemonsets=true avoids topolvm-node deletion.
  2. Reboot the node.
  3. Run kubectl uncordon NODE after the node comes back online.
  4. After reboot, Pods will be rescheduled to the same node because PVCs remain intact.

Limitations

See limitations.md.