이 콘텐츠는 선택한 언어로 제공되지 않습니다.
Chapter 7. 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.
7.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,snapshot-webhook, ornone.noneis mutually exclusive with all other values.NoteIf the
optionalCsiComponentsvalue is empty or null, MicroShift defaults to deploying snapshot-controller and snapshot-webhook.
-
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
NoteMicroShift does not redeploy the disabled components after a restart.
7.2. Disabling deployments that run the CSI driver 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 driver implementation will be running. Users must manually remove it by following the uninstallation instructions.
MicroShift will not delete CSI driver implementation pods. You must configure MicroShift to disable installation of the CSI driver implementation pods during the startup process.
Procedure
Disable installation of the CSI driver by entering the
drivervalue under thestoragesection of the MicroShift configuration file in/etc/microshift/config.yaml:# ... storage driver: - "none" 1 # ...- 1
- Valid values are
noneorlvms.
NoteBy default, the
drivervalue is empty or null and LVMS is deployed.Start MicroShift after the
driverfield is specified with a supported value in the/etc/microshift/config.yamlfile by running the following command:$ sudo systemctl enable --now microshift
NoteMicroShift does not redeploy the disabled components after a restart operation.
