Setting up Data Manager housekeeping service

When Data Manager exceeds its allocated disk space, the background housekeeping service begins to delete volume scans, starting from the oldest.

Data Manager disk space is allocated during installation, but can be modified later on.

Log in to the server as root.
Open the file /etc/vaisala/focus/k8s/vaisala-focus.yaml in your favourite editor, for example vi or emacs, and edit the necessary parameters under datamanager:
```
volumedir:maxSizeMB: 66850
fixedDelay:          ms: 60000
fixedRate:          ms: 3600000
```
The disk space allocation for Data Manager is configured during installation. If you wish to change the allocation later on, use the datamanager.volumeDir.maxSizeMB parameter. For example: datamanager.volumeDir.maxSizeMB = 1000
```
datamanager.volumeDir.maxSizeMB = 1000
```
Define how often housekeeping checks for disk overusage (milliseconds).
```
datamanager.housekeeping.fixedRate.ms = 60000
```
Vaisala recommends running this check once a day.

While this checks runs, other operations on Data Manager slow down.
Define the delay for when housekeeping first runs after Data Manager has been started or restarted (milliseconds).
```
datamanager.housekeeping.fixedDelay.ms = 60000
```

After making any changes, run:

kubectl apply -f /etc/vaisala/focus/k8s/vaisala-focus.yaml
kubectl get all -n vaisala-focus | grep pod/data-manager (this will show you the correct name for the next step)
kubectl delete pod <pod name> -n vaisala-focus        (example pod name: data-manager-service-5c9cd95ccb-b8str)