charts

There is one network entry point per deployment of our app infrastructure (eg. US and EU deploys), so the lambda does go and update both security groups simultaneously to allow the requestor's IP to hit either if they would like. If you wanted to, you could certainly make it more fine-grained than that, but the goal was simply to cut off the majority of the Internet from these mechanisms as an extra protection layer. There are all the other protection mechanisms (e.g. the mutual certs) to actually protect and authenticate the connection itself. For web apps, we simply front using an OAuth2-aware proxy. Back in the day, we used this: https://mattslifebytes.com/2018/08/07/protecting-internal-ap... Now, we utilize Kubernetes for hosting most production internal apps, so we run the oauth2-proxy Helm chart (https://github.com/helm/charts/tr

That's the values file. The actual manifest templates are just as horrifyingly impressive :). https://github.com/helm/charts/tree/master/stable/prometheus...

For anyone curious, this is what the prometheus chart look like (I think): https://github.com/helm/charts/blob/master/stable/prometheus...

The complaints about Lisp parentheses sound especially funny in the context of that kind of mainstream DevOps tooling https://github.com/helm/charts/blob/eceb82f6308578b824d58f80... (EDIT: yep, I'm a Lisp fan and a Kubernetes guy at the same time, and this kind of templating is like worst kind of "blasphemy" for me :)

Yeah, the core reason to use Helm is for the ecosystem. The value that comes from being able to quickly set up and compose packages on https://github.com/helm/charts/ is larger than the (very) annoying YAML templating and chart reliability issues. Lots of Helm charts have bugs, but lots of PyPI/NPM/Maven packages have bugs as well. Jsonnet, Cue, and operators are nice, but unless someone can create an ecosystem that is as valuable as the Helm ecosystem, I don't see Helm disappearing.

I don't think there is anything stopping you from bundling multiple services/deployments in the same helm chart. Many of the "curated" helm charts do it: https://github.com/helm/charts

I was trying to get airflow (https://airflow.apache.org/) up and running in the cloud. It has a few moving pieces that I didn't want to worry about. So I used a helm chart to install it - https://github.com/helm/charts/blob/master/stable/airflow Maybe this is overkill but it was reasonably quick to get up and running, scaling workers will be trivial, and the Airflow Kubernetes Operator opens up a lot of options for tasks. The vanilla install was pretty quick. Understanding the configurations took a bit more time. I would like to hear other thoughts about simpler ways to deploy this that don't require Kubernetes.

I actually have, and even better it can easily be setup with Helm on a Kubernetes cluster: https://github.com/helm/charts/tree/master/stable/phabricato...

From my experience, while YAML itself is something one can learn to live with, the true horror starts when people start using text template engines to generate YAML. Like it's done in Helm charts, for example, https://github.com/helm/charts/blob/master/stable/grafana/te... Aren't these "indent" filters beautiful?

I had to go through this last year with my previous company. Splunk's licensing is outrageous. They cap the data transfer on a PAID license arbitrarily. Even getting coordinated with their sales to just pay them was a chore. They do nothing to foster open development on their platform. IMO, the open offerings actually seem designed to make it impossible to improve/contribute/extend in a cost effective way. It is also ill equipped to deal with Kubernetes even though they did release a reasonable if Windows Guy bloated example of a k8s deployment at the beginning of this year. I was completely baffled when I found out it was a Django project. It feels like something from the depths of enterprise Java. Elasticsearch (or ELK/EFK) is really eating their lunch but if you have any experience managing an Elasticsearch cluster at scale you might h

Looks like there's a mongodb helm chart that uses stateful sets: https://github.com/helm/charts/tree/master/stable/mongodb

There's a helm chart available for Concourse, I haven't tried it yet though. Definitely agree about BOSH making it harder to get started. https://github.com/helm/charts/tree/master/stable/concourse

> I don't think anyone wants to use Helm. Here is why everyone should use Helm: Helm 2.0 introduced package as a first-class concept for Kubernetes and created the standard to distribute applications, thanks to Helm thousands of people could discover and collaborate on cloud-native deployments of the open source software https://github.com/helm/charts/tree/master/stable published and managed by organizations and contributors all over the world. Helm 3.0 keeps innovating, it adopts the most forward-thinking approach to package management and Kubernetes config management by using higher level domain specific language based on Lua to create expressive package management system: https://sweetcode.io/a-first-look-at-the-helm-3-plan/ Helm is also backed by CNCF[1] and is the best choice so far for organizations to create a reproducible CI/CD pi

There's a helm chart for that :) https://github.com/helm/charts/tree/master/stable/kong

There are a few options to deploy Kong as your API Gateway: Kong can work as an Ingress Controller for your Kubernetes cluster and run plugins for your traffic at the Ingress layer. Refere to the repo for more details: https://github.com/kong/kubernetes-ingress-controller You can simply deploy it as an application using the Helm chart: https://github.com/helm/charts/tree/master/stable/kong