[bitnami/mysql] helm default resource values are too low

[m-niak]

Name and Version

bitnami/mysql latest

What architecture are you using?

arm64

What steps will reproduce the bug?

you should increase default request and limit resource for mysql , because all health probes keeps failing , and mysql process can't start .
current : 256Mi
offer : 1Gi

Are you using any custom parameters or values?

No response

What is the expected behavior?

No response

What do you see instead?

error: 'can't connect to local mysql server through socket '/opt/bitnami/mysql/tmp/mysql.sock' (2)' check that mysqld is running and that the socket: '/opt/bitnami/mysql/tmp/mysql.sock' exists!

Additional information

No response

[javsalgar]

Hi,

As stated in #24251, in the chart documentation and the installation notes, the resourcesPreset value are not meant for production workloads, but for testing. In fact, we use the minimum value that works in our automated testing in all K8s distributions.

For production you should use the resources value, setting the values adapted to your use case.

[m-niak]

I understand and I mean you can't even init mysql with your default resource values !
POD status will not be running .

[javsalgar]

Which are the specs of your Kubernetes cluster? We are able to deploy without issues in minikube, gke and all major k8s distributions.

[github-actions]

This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.

[github-actions]

Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary.