Quantcast
Channel: User BvuRVKyUVlViVIc7 - Stack Overflow
Viewing all articles
Browse latest Browse all 42

helmfile best practices with multiple customers

$
0
0

We would like to have some recommendations, since we want to integrate helmfile in our deployment process...

Our infrastructure has following details:

  • we have many customers
  • all customers have the same installed services(each customer get's it's own services, no sharing between customers)
  • credentials are different for each customer
  • we prefer a seperatedeployment process (we dont want to upgrade all customers at the sametime)
  • all customer-config data is seperated into seperate configfiles, like:
    • config/customer1.yaml
    • config/customer2.yaml
    • config/customer3.yaml

So I'm wondering, if we should use "Environment" with the customer name, to upgrade it.. or would you recommend another variable?And do you think it's better to create multiple helmfiles for this process, or just one?

Thank you!


Viewing all articles
Browse latest Browse all 42

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>