You can view the current amount of disk space allocated for the operation of KUMA Core and the Metrics service. If required, you can change the allocated disk space.
Viewing the currently allocated disk space
The commands for viewing the disk space do not affect the operation of the running services.
To view the disk space allocated for KUMA Core:
On the administrator host, run the following command:
./kdt invoke kuma --action getCorePvcSize
To view the disk space allocated for the Metrics service:
On the administrator host, run the following command:
./kdt invoke kuma --action getMetricsPvcSize
Changing the currently allocated disk space
The commands change the core_disk_request
and the metrics_disk_request
parameters. When you run a command, the corresponding service is stopped, the disk space is changed, and the service is restarted. The application updates the core_disk_request
and metrics_disk_request
parameters only if the commands are successfully completed.
You can only enlarge the current disk space. If you try to set a disk space value smaller than the current one, a command returns an error. In this case, the services do not stop.
If an error occurs after the services have already been stopped, the application tries to restart the services and keep the previous disk space value.
To change the disk space allocated for KUMA Core:
On the administrator host, run the following command:
./kdt invoke kuma --action setCorePvcSize --param core_disk_request=<
value
>
where <
value
>
is new disk space size, for example 50Gi
.
To change the disk space allocated for the Metrics service:
On the administrator host, run the following command:
./kdt invoke kuma --action setMetricsPvcSize --param metrics_disk_request=<
value
>
where <
value
>
is new disk space size, for example 50Gi
.