Questo contenuto non è disponibile nella lingua selezionata.
Chapter 6. Disabling the LVMS CSI provider or CSI snapshot
To reduce use of runtime resources such as RAM, CPU, and storage in MicroShift, you can disable the built-in LVMS CSI provider or CSI snapshot. Configure the storage section in the configuration file before you install or run the product.
6.1. Disabling deployments that run CSI snapshot implementations Copia collegamentoCollegamento copiato negli appunti!
To prevent the installation of CSI implementation pods, disable the deployments that run CSI snapshot implementations. This configuration conserves system resources by ensuring that snapshot components are not deployed when they are not required.
Use the procedure if you are defining the configuration file before installing and running MicroShift. If MicroShift is already started, the CSI snapshot implementation will be running. You must manually remove the implementation by following the uninstallation instructions.
MicroShift does 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: {} # ...where:
storageSpecifies the storage details. You can choose to not define
optionalCsiComponents. If you do specify theoptionalCsiComponentsfield, valid values include: an empty value ([]) or a single empty string element ([""]),snapshot-controller, ornone. A value ofnoneis mutually exclusive with all other values.NoteIf the
optionalCsiComponentsvalue is empty or null, MicroShift defaults to deployingsnapshot-controller.
After the
optionalCsiComponentsfield is specified with a supported value in theconfig.yaml, start MicroShift by running the following command:$ sudo systemctl start microshiftNoteMicroShift does not redeploy the disabled components after a restart.
6.2. Disabling deployments that run the CSI driver implementations Copia collegamentoCollegamento copiato negli appunti!
You can disable installation of the CSI implementation pods. MicroShift does not delete CSI driver implementation pods. You must configure MicroShift to disable installation of the CSI driver implementation pods during the startup process.
This procedure is for defining the configuration file before installing and running MicroShift. If MicroShift is already started, then the CSI driver implementation is running. You must manually remove it by following the uninstallation instructions.
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" # ...where:
storage.driver.noneSpecifies the driver to disable. 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 microshiftNoteMicroShift does not redeploy the disabled components after a restart operation.