Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VolumeSnapshotContent RestoreSize field missing when using Velero #181

Open
2 tasks
skhalash opened this issue Feb 10, 2025 · 0 comments
Open
2 tasks

VolumeSnapshotContent RestoreSize field missing when using Velero #181

skhalash opened this issue Feb 10, 2025 · 0 comments

Comments

@skhalash
Copy link
Contributor

skhalash commented Feb 10, 2025

Description

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
@skhalash skhalash added the kind/bug Something isn't working label Feb 10, 2025
@a-thaler a-thaler removed the kind/bug Something isn't working label Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants