Ensuring that configuration is up to date is difficult with any infrastructure; With Kubernetes and the lack of versioned ConfigMaps, this problem is amplified.
At Pusher, we have a number of applications that can’t dynamically reload their configuration. Over the last two years, this has caused pain for our engineers and made deploying new configuration hard.
In this post I explore our new project Wave and how we solved the problem of ensuring that our application’s running configuration matches the desired configuration.