Loading…
Images, layers, networking, volumes, then pods, services, deployments and scaling.
Your team builds a separate container image for development, staging and production because each one has a different API base URL and log level baked in. What is a ConfigMap, and how would it change this setup?
A colleague says "Secrets are encrypted, so it's fine that anyone on
the team can kubectl get secret -o yaml." What is the real difference
between a Secret and a ConfigMap, and what is wrong with that
statement?
Read this container spec. Where does each setting come from, and how will the app see it?
A pull request adds k8s/secret.yaml containing the production
database password, so that kubectl apply -f k8s/ creates everything
in one go. Why should this be rejected, and how else can the Secret be
created?
What is the value of api-key in this Secret, and why does the second
Secret, written with stringData, end up looking similar after you
apply it and read it back?
You changed LOG_LEVEL from info to debug in the api-config
ConfigMap and applied it, but the running pods still log at info level
an hour later. The pods read the value through envFrom. Why, and how
do you make them pick it up?