Kanister Blueprint for MySQL fails

Hello @meijianwei,

Thank you for using K10 community!

There are a few Blueprint templates at K10's official documentation that are supported, and can be used as an example for testing together with the supported helm charts. 

The blueprints for logical backups can be found here:

https://docs.kasten.io/latest/kanister/testing.html#logical-backups

MySQL:

https://docs.kasten.io/latest/kanister/mysql/install.html

MySQL Openshift:

https://docs.kasten.io/latest/kanister/mysql/install_logical_os.html

Have checked K10 MySQL Blueprints and followed the example in the page above and it is working.

I am not sure from the outputs you've sent, if you are using the blueprint from K10 docs and bitnami helm chart (https://charts.bitnami.com/bitnami) that this MySQL Blueprint supports, If you are using a different helm chart or blueprint, you might have to adapt it to the specific parameters, secrets and so on.

If you want to troubleshoot what is happening during the backup with the blueprint, please monitor the kanister logs while running the backup, it might point you to the issue:

kubectl get pods --no-headers -n kasten-io | grep kanister | awk '{print $1}' | xargs kubectl logs -n kasten-io -f

 

FRubens

Hello @meijianwei,

I would recommend checking the repository of mysql-sidecar image in your blueprint, it shows that you are using registry.example.com:8443 that is not a real repository, you might get it from ghcr.io as in the original Blueprint or if you have a private repo please replace registry.example.com with your image repository and try again:
 

@meijianwei ,Thanks for clarifying.

I would recommend trying to follow the blueprint steps manually and check if there are any issues.

Bash into the mysql pod/container and run the same command of the blueprint in the phase "dumptostore", and check the output, it might help to find if there is any issues with the commands.

Try to follow the steps and see if there is anything wrong, since you are not using bitnami chart where this Blueprint was designed and tested, I am not sure what else you must change or even add to make the blueprint work for your MySQL installation, you might need to find out if there is anything missing, or even write your own blueprint.

On K10 side, kanister logs would help you to find out what is happening, you can keep monitoring kanister logs while testing the blueprint, you can possibly monitor the pods in the MySQL namespace and try to get the logs from the kanister pod when it is created since it is running the BP commands, it might be for a short time, but if you manage it can help.