Summary
KubeBlocks supports configuration re-rendering for several resource or topology changes through reRenderResourceTypes, but it does not currently have a trigger for disk/PVC expansion. This makes some addons keep stale disk-capacity-derived configuration after a successful VolumeExpansion operation.
This issue requests a new reRenderResourceTypes value, such as volumeExpansion, and the corresponding controller trigger so addons can opt in to configuration re-rendering after volume expansion. Please also consider picking this improvement back to release-1.0.
Is your improvement request related to a problem? Please describe.
Some addons render database configuration values from component volume claim sizes. For example, a database engine may size local cache, local storage quota, or other disk-capacity-derived parameters from the data PVC capacity by using KubeBlocks template functions during configuration rendering.
Today, CPU and memory changes can trigger configuration re-rendering through reRenderResourceTypes: [vscale], so parameters derived from container resources can be refreshed after a VerticalScaling operation.
However, VolumeExpansion does not have an equivalent reRenderResourceTypes trigger. After a PVC is expanded, the rendered ConfigMap and the runtime configuration can still keep the old disk-derived value because the ComponentParameter payload/revision is not updated.
Summary
KubeBlocks supports configuration re-rendering for several resource or topology changes through
reRenderResourceTypes, but it does not currently have a trigger for disk/PVC expansion. This makes some addons keep stale disk-capacity-derived configuration after a successfulVolumeExpansionoperation.This issue requests a new
reRenderResourceTypesvalue, such asvolumeExpansion, and the corresponding controller trigger so addons can opt in to configuration re-rendering after volume expansion. Please also consider picking this improvement back torelease-1.0.Is your improvement request related to a problem? Please describe.
Some addons render database configuration values from component volume claim sizes. For example, a database engine may size local cache, local storage quota, or other disk-capacity-derived parameters from the
dataPVC capacity by using KubeBlocks template functions during configuration rendering.Today, CPU and memory changes can trigger configuration re-rendering through
reRenderResourceTypes: [vscale], so parameters derived from container resources can be refreshed after aVerticalScalingoperation.However,
VolumeExpansiondoes not have an equivalentreRenderResourceTypestrigger. After a PVC is expanded, the rendered ConfigMap and the runtime configuration can still keep the old disk-derived value because theComponentParameterpayload/revision is not updated.