A developer needs a ConfigMap holding a non-sensitive database host…

Question

A developer needs a ConfigMap holding a non-sensitive database host for a city permits app using kubectl. Which approach correctly creates that configuration object?

Accepted Answer

kubectl create configmap permits-db --from-literal=host=db.permits.svc — ConfigMaps are the labeled cubbies for plain settings like a DB hostname. kubectl create configmap --from-literal fills a cubby without pretending the value is a Secret. expose and raw Pod env alone are different tools.

Answer

kubectl create secret generic db-host --from-literal=host=db.permits.svc so ConfigMaps stay empty

Answer

kubectl apply -f a Pod that embeds the host only in an env value without any ConfigMap API object

Answer

kubectl expose deployment permits --port=5432, which auto-creates a ConfigMap named permits-db

A developer needs a ConfigMap holding a non-sensitive database host for a city permits app using kubectl. Which approach correctly creates that configuration object?

Short Explanation

Full Explanation