This change improves chart clarity and avoids user confusion when MySQL fails to start on these minimal presets.

Updates the comment for the resourcesPreset field in bitnami/mysql/values.yaml to clarify that the nano and micro presets are not recommended or supported for MySQL due to insufficient CPU/memory for successful startup.

These presets frequently lead to:
- liveness/readiness probe failures
- slow initialization causing startupProbe timeouts
- OOMKilled container terminations
- MySQL never becoming Ready

Signed-off-by: Muthukumaran <[email protected]>

Author: muthukumaran-muthiah

bitnami/mysql/values.yaml

@@ -422,6 +422,7 @@ primary:
   ## resources, such as Minikube. If you do want to specify resources, uncomment the following
   ## lines, adjust them as necessary, and remove the curly braces after 'resources:'.
   ## @param primary.resourcesPreset Set container resources according to one common preset (allowed values: none, nano, micro, small, medium, large, xlarge, 2xlarge). This is ignored if primary.resources is set (primary.resources is recommended for production).
+  ## NOTE: The "nano" and "micro" presets allocate extremely low CPU/memory. These values may cause MySQL to fail during startup (e.g., OOMKilled, readiness/liveness probe failures)
   ## More information: https://github.com/bitnami/charts/blob/main/bitnami/common/templates/_resources.tpl#L15
   ##
   resourcesPreset: "small"