Helm

Comparison I have to disclaim that due to my limitation of knowledge, the following is just my personal opinion(according to my experience). So there may be some errors or omissions. If you have any suggestions, please let me know. Feature MySQL Operator Bitnami MySQL Percona XtraDB Cluster High Availability Yes Yes Yes Automatic Failover Yes No Yes Backup/Restore Yes No Yes Scaling Yes Limited Yes Custom Configurations Yes Limited Yes Multi-Master Replication Yes No Yes Ease of Setup Moderate Simple Moderate Community Support Weak Strong Strong Cloud Native Yes No Yes Installation Bitnami MySQL As to my concern, the bitnami one does not have a failover solution, so if the mater is down, it will be down for sure....

Helm Charts here, I use terraform + helm provider to install teleport charts. We have to start from here: https://goteleport.com/docs/reference/helm-reference/ For a K8s cluster, we need at least install no less than two components: teleport-cluster teleport-operator is included teleport-kube-agent A few steps further: setup Github Login setup applications Also, we need cert-manager to issue certificates. As we need DNS solver, this means we need to create a TXT record of that domain every time when we issue a wildcard domain to get verified by ACME, which means we need to configure according to different DNS providers....

Sometimes if we do not pay attention to the helm release uninstallation order, like we removed one release which includes CRDs and then we try to remove a customized resource which does not have a reference or finalization, that means this resource will cause resource recycle stuck, in other words, the helm release stuck at “uninstalling” status. There is a quick fix which can easily sort it out. helm plugin install https://github....