With Kubernetes or any container orchestrator, you have an interesting mix of configuration options. Kubernetes runs your containers for you. There is no way to set different environment options and command-line arguments for a specific run because Kubernetes decides when and where to run your container. What you can do is embed configuration files in your Docker image or change the command it is running; however, that means baking a new image for each configuration change and deploying it to your cluster. It's not the end of the world, but it's a heavyweight operation. You can also use the dynamic configuration options I mentioned earlier:
- Remote configuration store
- Remote configuration service
However, Kubernetes has some very neat tricks when it comes to dynamic configuration. The most innovative dynamic configuration mechanism...