The example to connect to the MySQL with the secret is no longer working

[winem]

Hi,

first of all, I'm new to the mysql-operator and am quite happy so far. The operator seems to be the best choice to manager users, databases and permissions without having tons of overhead or capabilities one may not need.

I already noticed that a few parts of the documentation are outdated and will provide a PR to align the examples with the latest code soon.

There is just one thing I can not figure out:
The instructions on "Connect to MySQL with the secret" are:
kubectl exec -it $(kubectl get po | grep mysql | head -1 | awk '{print $1}') -- mysql -usample-user -p$(kubectl get secret mysql-mysql-sample-nakamasato -o jsonpath='{.data.password}' | base64 --decode)

This results in:

error: Internal error occurred: error executing command in container: failed to exec in container: failed to start exec "e98fa494388c9fd3ab7a9b9b0bc3f2e41dbb6a9f9004d1f94a462f6587dea4f4": OCI runtime exec failed: exec failed: unable to start container process: exec: "mysql": executable file not found in $PATH: unknown

My next attempt was to enter the pod and run sh or bash - which did not work either. So I assume that the container is a distroless one now. Is that correct? I'd love to have any opportunity to inspect the MySQL database via the console without having to run additional containers or helm charts. Is that possible right now?

If not, it may be an option to add a small mysql container as a sidecar if some flag is provided.

Thanks in advance,
Marcel

[winem]

This also affects the step where permissions of the user are set via GRANT ...

Any feedback is appreciated and I'd even be happy to help with the solution once we agree on some way to go.

[nakamasato]

Sorry for the late reply. Does this still happen?