But this can lead to tight, implicit coupling between your project and Kubernetes. Helm and ConfigMaps are optional features so you don’t have to use them. Especially when merging multiple config files or adding more services to a pod, this can get quite confusing quickly. Kubernetes - or helm, for that matter - allows injecting external configs dynamically to ensure separation of concerns. Logic on which we implicitly relied on. As an example, Kubernetes allows embedding service configurations using ConfigMaps. in development). Have a common place to share configurations and secrets. Provide an endpoint for metrics and logging. Why Kubernetes was not a good fit for us When creating a prototype with Kubernetes, we noticed that we started adding ever-more complex layers of logic to operate our services. We needed a simple system to keep those jobs running. We started with a list of requirements for container orchestration: Run a fleet of services across many machines. Provide an overview of running services. Allow for communication between services. Restart them automatically when they die. Be manageable by a small team. On top of that, the following things were nice to have but not strictly required: Tag machines by their capabilities (e.g., label machines with fast disks for I/O heavy services.) Be able to run these services independently of any orchestrator (e.g. So we looked into alternatives - and fell in love with Nomad. The wishlist Our team runs a number of typical services for monitoring and performance analysis: API endpoints for metrics written in Go, Prometheus exporters, log parsers like Logstash or Gollum, and databases like InfluxDB or Elasticsearch. Each of these services run in their own container. For what our team of four wanted to achieve at trivago, it added too much overhead. 'body': ' A woman riding a scooter Illustration created by freepik, Nomad logo by HashiCorp. Kubernetes is the 800-pound gorilla of container orchestration. It powers some of the biggest deployments worldwide, but it comes with a price tag. Especially for smaller teams, it can be time-consuming to maintain and has a steep learning curve.

'title': 'Maybe You Don't Need Kubernetes ',

Brew macvim cannot allocate color