This post is just a set of short meeting notes from CNCF Workshop (Helm Workshop: v2 to v3), but I think it will be useful.

- Use stable releases. Always. And wait for fixes, before upgrade.
- Combine tools. Do not try to Terraform everything.
- Do not treat examples as well-defined solutions.
- Automate. Do not plan or apply manually.
- Do not do things manually. Never.
- Test additive and fresh-start change.
- Separate modules wisely.
- Use tools to test code statically, resources quality and security.
- Use functions accordingly.
- Do not overkill modules with variables. 
- Manage provider versions.

version-checker is a Kubernetes utility for observing the current versions of images running in the cluster, as well as the latest available upstream. These checks get exposed as Prometheus metrics to be viewed on a dashboard, or soft alert cluster operators.

Klepto helps you to keep the data in your environment as consistent as possible by copying it from another environment's database.

You can use Klepto to get production data but without sensitive customer information for your testing or local debugging.

- Do not store secrets in environment variables
- Only use trusted base images
- Do not use ‘latest’ tag for base image
- Avoid curl bashing
- Do not upgrade your system packages
- Do not use ADD if possible
- Do not root
- Do not sudo

Replicated Troubleshoot is a framework for collecting, redacting, and analyzing highly customizable diagnostic information about a Kubernetes cluster. Troubleshoot specs are created by 3rd-party application developers/maintainers and run by cluster operators in the initial and ongoing operation of those applications.

Learn how to set up the Kubernetes cluster in 30 mins and deploy the application inside the cluster.

In this blog post, we’ll look at the business value of SRE through customer focus, observability, and efficiency.