This guide describes how the different storage volumes are used by Dynatrace Operator.
The following table shows the storage requirements of Dynatrace Operator deployment modes.
The kubelet root directory is the central storage location for all directories required by the CSI driver. Allocate approximately 30 GB for the kubelet directory to cover all Dynatrace-related storage requirements.
These numbers should be increased for volatile environments and can be decreased for environments with disk space monitoring.
Depending on your setup, the kubelet root directory might not be located in /var/lib/kubelet.
Contains the CSI driver components and enables kubelet to interact with the driver for operations like health checks.
Storage usage depends on your environment:
If OneAgent is monitoring the host additional storage is consumed.
| Component | Disk usage | Notes |
|---|---|---|
| OneAgent | 5 GB | Essential for OneAgent functionality. |
| Code Modules | see table below 1 | |
| Runtime logs | 0.1-1 GB per pod | Logs and data generated at runtime. |
| Configuration | 20 MB per pod |
Disk usage per version is depending on the architecture. Without CSI driver the listed amount of storage is consumed per pod.
| Architecture | Disk usage |
|---|---|
| amd64 | 1.2 GB |
| arm64 | 800 MB |
| s390x | 500 MB |
| ppc64le | 500 MB |
Allows the Extension Execution Controller to store configuration, runtime data, logs, and secrets required for executing extensions.
Allows the SQL Extension Executor to store temporary files (for example, certificates).
Allows the OneAgent to persist its configuration.
Configurable using storageHostPath field in the Dynakube. See Dynakube parameters for more information.
These directories are specific to Dynatrace. They are injected into workloads by the Webhook and don't require user management or configuration.
Same disk usage as described in plugin directory disk usage. You can save storage by configuring the node image pull feature.
More details about the format of <size> can be found in the Kubernetes documentation.
Overview of the volume size limits for ephemeral volumes of the Dynatrace Operator components and which Helm switches can be used to configure them.
| Component | Container(s) | Volume name | Mount point | Helm value | Size limit default |
|---|---|---|---|---|---|
| dynatrace-webhook | webhook | certs-dir | /tmp/k8s-webhook-server/serving-certs | webhook.volumes.certsDir.sizeLimit | 10 Mi |
There are no default values for ephemeral storage resource configuration. They can be configured using the Helm switches shown in the following table:
The Helm switches can be used in a custom values.yaml file to control the limits during Operator install with the Helm chart.