3 ms·

Question for those running kubernetes/nomad for dev/alpha/beta/prod: - are changes promoted and pushed automatically dev to beta to prod - or is there a inter

by scrubs 4y ago

Question for those running kubernetes/nomad for dev/alpha/beta/prod: - are changes promoted and pushed automatically dev to beta to prod - or is there a internal ticketing/admin system that collects requests to promote and install new container versions that when approved are only then run through k8s etc This is one aspect of deployment I don't see much of in the context of containers/orchestration and the rest

ngc248 4y ago
In our company, From dev to integration to QA cluster it is an automated push, At each stage tests are run and if all of em pass, auto pushed to the next stage. From QA to staging and production, it is a manual push.
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 ago
  Yea we used ArgoCD with our k8s cluster too at my previous job. And all the merges were done on Github.
ec109685 4y ago
Automated deployments from test, canary to production, done region by region. Happens when operating team is ready for a new release.
agumonkey 4y ago
And I'd like to know who set up an automated feature branch deployment on test servers ? I liked it when using some hosting platforms for small side projects but I've never used it on company large ones.
John23832 4y ago
We CD to dev, and cut releases to prod. Do both using ArgoCD. This is really an aspect of you CD system, rather than Kubernetes though.

by scrubs 4y ago

ngc248 4y ago

In our company, From dev to integration to QA cluster it is an automated push, At each stage tests are run and if all of em pass, auto pushed to the next stage. From QA to staging and production, it is a manual push.

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 ago
Yea we used ArgoCD with our k8s cluster too at my previous job. And all the merges were done on Github.

ec109685 4y ago

Automated deployments from test, canary to production, done region by region. Happens when operating team is ready for a new release.

agumonkey 4y ago

And I'd like to know who set up an automated feature branch deployment on test servers ? I liked it when using some hosting platforms for small side projects but I've never used it on company large ones.

John23832 4y ago

We CD to dev, and cut releases to prod. Do both using ArgoCD. This is really an aspect of you CD system, rather than Kubernetes though.