You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the measurement process relies on the RestoreSize field of VolumeSnapshotContent to determine the size. Recent incidents have revealed that this field is not consistently available, leading to inaccuracies in size calculations. When creating backups or restoring from backups using Velero, VolumeSnapshotContent is generated as a by-product, and in some cases, it lacks the RestoreSize field. This issue occurs despite the snapshot being backed by a billable hyperscaler resource.
Goal: Metering for VSC should happen only if the VSC is backed by the attached hyperscaler account, not any other account
Tasks:
Preparation
Investigate what CSI drivers are available in a kyma runtime
Understand if the driver selection indicates the fact to meter or not
Understand if the RestoreSize attribute is reliable in the metering scenario
Understand if the same knowledge can be applied to volumes
Implementation
The text was updated successfully, but these errors were encountered:
Description
Currently, the measurement process relies on the
RestoreSize
field ofVolumeSnapshotContent
to determine the size. Recent incidents have revealed that this field is not consistently available, leading to inaccuracies in size calculations. When creating backups or restoring from backups using Velero,VolumeSnapshotContent
is generated as a by-product, and in some cases, it lacks theRestoreSize
field. This issue occurs despite the snapshot being backed by a billable hyperscaler resource.Goal: Metering for VSC should happen only if the VSC is backed by the attached hyperscaler account, not any other account
Tasks:
The text was updated successfully, but these errors were encountered: