Moving from Heroku to Google Kubernetes Engine

Re:Moving from Heroku to Google Kubernetes Engine by Rotareti on Friday April 05, 2019 @06:19AM (#19581186)

> Like any package manager it's somewhat difficult to write good packages that have all these attributes. And I think you have to admit that a well-written helm chart that covers all the bases is a lot less readable (albeit much more powerful, stipulated) than a simple yaml description of the object you want.

I agree to that, but I think the situations in which you have to write really flexible and complex charts are pretty rare. Most of the charts that we maintain and use internally, use very little templating, because they are tailored to fit our own environments, not every environment under the sun.

[ Parent | on HN ]

Re:Moving from Heroku to Google Kubernetes Engine by techntoke on Friday April 05, 2019 @02:38PM (#19585690)

There are situations where it makes sense to create a shared chart that can be used by multiple teams to implement their services, but to be extensible enough to work with other common services. For example, cert-manager and external-dns. Or for a local environment, you may want to use Minio for AWS-compatible storage but Service Catalog and AWS Service Broker for other environments.

[ Parent | on HN ]