Re: Helm for Microservices Deployments
Loritsch, Berin <bloritsch@...>
toggle quoted messageShow quoted text
The complication I have is that the customer I have has very outdated concepts for approving and managing deployments. As a result, our devops pipeline is segregated from the production environment. However as part of the delivery we can provide the containers and helm charts for all the pieces. Once we get the go-ahead from the approval body we can run the "helm install" or "helm upgrade" process for the whole app.
It is our full intention to have sub-charts at least for each microservice should this archaic business process be brought into the 21st century. However, in the interim we will need a master chart to define the entire application. I did find a good approach for using labels to address some parts ot the problem: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels/
Thanks for the pointer to helmfile. I will look at that to see if I can use it to manage our deployments. We manage our dev and QA instances of the application using full DevOps. The disconnect comes in when we have to manage an acceptance test and production instance of the application on our customer's private cloud. Each of those environments requires some customization so we can point at managed resources without risking production problems.
On Fri, Jun 26, 2020 at 11:49 AM Paul Czarkowski <pczarkowski@...> wrote: