2 ms·
In our case: - We use ArgoCD to manage k8s deployments. - Every new build can be pushed to dev or QA by a trivial operation, a commit to a repo. It does not h
by nine_k 4y ago
In our case:
- We use ArgoCD to manage k8s deployments.
- Every new build can be pushed to dev or QA by a trivial operation, a commit to a repo. It does not happen automatically but would be trivial to make it so. We have more than one environment (dev, integration, QA), and plan to become able to spin up more on demand.
- A release is cut at a particular commit of the main branch, or, in rare cases, from a release-hotfix branch. After thorough testing, it is trivially pushed to prod, again, by making one commit and pushing it.
- The same way, everything can be rolled back by reverting a commit and pushing to the repo.
At one of my previous jobs, we used Spinnaker, and it was even more streamlined: pick the right container versions from a GUI.
- Alifatisk 4y agoYea we used ArgoCD with our k8s cluster too at my previous job. And all the merges were done on Github.