The State of Kubernetes Configuration Management

The State of Kubernetes Configuration Management

  • February 7, 2019
Table of Contents

The State of Kubernetes Configuration Management

Configuration management is a hard, unsolved problem. We share some unique insights about the strengths and weaknesses of several popular K8s config management tools. Of all the problems we have confronted, the ones over which the most brainpower, ink, and code have been spilled are related to managing configurations.

— Brendan Burns, Brian Grant, David Oppenheimer, Eric Brewer, and John Wilkes, Google Inc. Configuration management is a hard, unsolved problem.

When we first started Argo CD, a GitOps deployment tool for Kubernetes, we knew we had to limit its scope to a deployment tool and not go anywhere near config management. We understood that since there was no perfect config management solution, Argo CD should remain agnostic to how kubernetes manifests are rendered, and let the user decide for themselves the right tool and workflow that works best for them.

Source: argoproj.io

Share :
comments powered by Disqus

Related Posts

APIServer dry-run and kubectl diff

APIServer dry-run and kubectl diff

Declarative configuration management, also known as configuration-as-code, is one of the key strengths of Kubernetes. It allows users to commit the desired state of the cluster, and to keep track of the different versions, improve auditing and automation through CI/CD pipelines. The Apply working-group is working on fixing some of the gaps, and is happy to announce that Kubernetes 1.13 promoted server-side dry-run and kubectl diff to beta.

Read More
Jaeger integration in Kiali

Jaeger integration in Kiali

Kiali has the ability to show traces obtained from Istio. Jaeger collects traces for monitoring and troubleshooting microservices-based distributed systems, and both Istio and Kiali use the data that Jaeger provides. Originally this was done via a separate tab in the UI.

Read More