[BUG] v-scale supports optional configuration re-rendering

[Y-Rookie]

In the current v-scale scenario of Redis, only the pod's resources are modified, but the kernel's maxmemory is not synchronously modified, causing v-scale to not take effect in practice.

The value of maxmemory is dynamically rendered in the template based on the Pod's resources. In the v-scale scenario, re-rendering is not triggered, hence leading to this problem.

[github-actions]

This issue has been marked as stale because it has been open for 30 days with no activity

[sophon-zt]

duplicated issue: #6273