An application image runs in multiple environments, with each environment using different certificates and ports.
Is this a way to provision configuration to containers at runtime?
Solution: Create images that contain the specific configuration for every environment.
Correct Answer: B
Explanation
= Creating images that contain the specific configuration for every environment is not a way to provision configuration to containers at runtime. This approach violates the principle of separating application code from configuration, and makes the images less portable and reusable across different environments1. It also increases the maintenance overhead and the risk of configuration drift, as any change in the configuration would require rebuilding and redeploying the images2. To provision configuration to containers at runtime, you should use a different mechanism, such as environment variables, command-line arguments, or config maps345. References:
* Configuration management with Containers | Kubernetes
* Environment variables in Compose | Docker Docs
* Override the default command | Docker Docs
* Configuration management with Containers | Kubernetes