A permits API must start with a feature flag and listen port taken from a ConfigMap without baking those values into the image. Which approach parameterizes startup args from that ConfigMap?
Select an answer to reveal the explanation.
Short Explanation
Think of ConfigMap env vars as sticky notes the process can read when it boots. Wire the keys into the container environment, then let command or args expand those variables so startup stays image-clean. Changing the ConfigMap (and rolling the Pod) updates flags without rebuilding.
Full Explanation
ConfigMaps commonly inject configuration as environment variables via env or envFrom. Those variables can parameterize container command and args so feature flags and listen ports are not baked into the image. hostPath and Namespace annotations are not the standard, portable mechanism for application startup arguments. After updating ConfigMap-backed env values, Pods typically need a restart or rollout to pick up the new process environment.