Red Hat build of MicroShift

Disable deployments that run CSI snapshot implementations

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 optionalCsiComponents value under the storage section of the MicroShift configuration file in /etc/microshift/config.yaml:
```
# ...
  storage: {}
# ...
```
where:

storage

Specifies the storage details. You can choose to not define optionalCsiComponents. If you do specify the optionalCsiComponents field, valid values include: an empty value ([]) or a single empty string element ([""]), snapshot-controller, or none. A value of none is mutually exclusive with all other values.

If the optionalCsiComponents value is empty or null, MicroShift defaults to deploying snapshot-controller.
After the optionalCsiComponents field is specified with a supported value in the config.yaml, start MicroShift by running the following command:
```
$ sudo systemctl start microshift
```
MicroShift does not redeploy the disabled components after a restart.