Some pods could crash and get evicted if a node becomes low on disk space.
If one or more pods running on the node produces a large volume of logs and the node's disk usage is high at the same time, it is possible to run out of ephemeral storage before periodic cleanup happens, leading to pod eviction.
If this occurs, increase the disk used by the object store for storing support bundle data using Fleet Manager APIs.
Method: POST
URL: https://<FleetManager hostname>/lcm/lcops/api/environments/<environment ID>/products/<product ID>/actions/invoke
Payload:
{
"name": "configure-packages",
"properties": {
"namespace": "vmsp-platform",
"name": "vmsp-platform",
"values": {"profiles":{"overrides":{"supportBundle":{"logOffloader":{"s3BucketRequests":{"size": "<value>"}}}}}}
},
"ref": "/webhooks/core/vmsp/configure"
}
where <value>
depends on the profile used (these are minimum recommended values, you can use larger ones):
Profile
|
Size
|
---|---|
small | 83Gi |
medium | 108Gi |
large | 183Gi |
Usually pod eviction leads to a temporary degradation of services with a subsequent recovery. However, if the disk size is not increased proactively or when this problem is observed, generated support bundles might miss the log data for the duration of degradation and recovery.