PVC auto scale on a per ordinal basis #380
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Main motivation:
Changes:
status.selfHealing
size, but rather the maximum of: {spec.volumeClaimTemplate.resources.storage
,spec.instanceOverrides[instanceName].volumeClaimTemplate.resources.storage
, or data source size, if a data source is configured either explicitly or viaautoDataSource
}status.selfHealing
is now maintained on a per-instance basis, so that storage expansion is minimized. Pods can have different storage sizes based on their needs.autoDataSource
to work with snapshots for same instance only with additionalmatchInstance: true