minimize created PVC size and expand only as needed on a per-PVC basis. Previously, it was always creating new PVCs with the latest auto scaled size, which meant that PVCs could not shrink on re-creation without re-creating the entire CosmosFullNode resource.
Allow autoDataSource to work with snapshots that are node-local
Changes:
New PVCs will not use the 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 via autoDataSource }
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.
Allow autoDataSource to work with snapshots for same instance only with additional matchInstance: true
Main motivation:
Changes:
status.selfHealingsize, 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.selfHealingis now maintained on a per-instance basis, so that storage expansion is minimized. Pods can have different storage sizes based on their needs.autoDataSourceto work with snapshots for same instance only with additionalmatchInstance: true