Best practices around versioning of workload configs

Kuberenetes best practices state that “Configuration files should be stored in version control before being pushed to the cluster. This allows you to quickly roll back a configuration change if necessary. It also aids cluster re-creation and restoration.”

What are the best practices for how this should be handled in Rancher where the UI, in theory, should be frequently used to modify the cluster state? Is there a way to have changes implemented in gui versioned in git without adding a lot of extra steps?

1 Like

Probably easiest way is to use GitLab: