第6章 Disabling the LVMS CSI provider or CSI snapshot
You can configure MicroShift to disable the built-in logical volume manager storage (LVMS) Container Storage Interface (CSI) provider or the CSI snapshot capabilities to reduce the use of runtime resources such as RAM, CPU, and storage.
6.1. Disabling deployments that run CSI snapshot implementations リンクのコピーリンクがクリップボードにコピーされました!
Use the following procedure to disable installation of the CSI implementation pods.
This procedure is for users who are defining the configuration file before installing and running MicroShift. If MicroShift is already started then CSI snapshot implementation will be running. Users must manually remove it by following the uninstallation instructions.
MicroShift will not delete CSI snapshot implementation pods. You must configure MicroShift to disable installation of the CSI snapshot implementation pods during the startup process.
Procedure
Disable installation of the CSI snapshot controller by entering the
optionalCsiComponentsvalue under thestoragesection of the MicroShift configuration file in/etc/microshift/config.yaml:# ... storage: {}1 # ...- 1
- Accepted values are:
-
Not defining
optionalCsiComponents. -
Specifying
optionalCsiComponentsfield with an empty value ([]) or a single empty string element ([""]). Specifying
optionalCsiComponentswith one of the accepted values which aresnapshot-controller, ornone. A value ofnoneis mutually exclusive with all other values.注記If the
optionalCsiComponentsvalue is empty or null, MicroShift defaults to deploying snapshot-controller.
-
Not defining
After the
optionalCsiComponentsfield is specified with a supported value in theconfig.yaml, start MicroShift by running the following command:$ sudo systemctl start microshift注記MicroShift does not redeploy the disabled components after a restart.