Storage requirements
The following table shows the storage requirements of Dynatrace Operator deployment types.
| Deployment type | Without CSI driver | With CSI driver1 | With CSI driver and code modules image |
|---|---|---|---|
classicFullStack | ~1,3 GB for OneAgent2 configuration/binaries (directly on the node) | N/A | N/A |
hostMonitoring | ~1,3 GB for OneAgent2 configuration/binaries (directly on the node) | ~1,3 GB for OneAgent2 configuration/binaries (on the node managed by CSI driver) | N/A |
applicationMonitoring | ~650 MB per monitored pod3 (in ephemeral storage, directly on the pod) | - ~650 MB per tenant and running OneAgent version4 - ~0,2 MB (and logs during runtime) per injected pod | - ~650 MB per running OneAgent version4 - ~0,2 MB (and logs during runtime) per injected pod |
cloudNativeFullStack | N/A (CSI driver required) | A combination between the following: - hostMonitoring with CSI driver- applicationMonitoring with CSI driver | A combination between the following: - hostMonitoring with CSI driver- applicationMonitoring with CSI driver and code modules image |
1 Used for read-only filesystem support (the default for host monitoring and cloud-native full-stack deployments). 2 New OneAgent versions overwrite old OneAgent versions. 3 If the pod is destroyed, OneAgent is automatically deleted. 4 Garbage collector removes old OneAgent versions that are no longer used within 60 minutes. |