The prebuilt Kubernetes path injects Meraki API credentials via Secret-mounted environment variables at deploy time. A teammate proposes baking the key into the image layers. Which choice follows the integration contract?
Select an answer to reveal the explanation.
Short Explanation
Don’t etch the vault combination into every crate stamp—hand the combination at delivery. Cluster Secrets and ConfigMaps inject at deploy; baking tokens into the image fails the contract.
Full Explanation
A prebuilt Kubernetes path injects environment or mounted Secret and ConfigMap values at deploy time. Baking a controller or Meraki token into the image so every tag carries it fails the integration contract and conflicts with secret-handling practice. Credentials stay out of the image; runtime injection supplies them.