configMapRef db-access not found

[robertmcnees]

The yml in module 1 section 4 be-deploy.yml and db-deploy.yml both make reference to a configMapRef that isn't in my environment or specified in the files given.
Have I missed where this is defined? I am getting Error: configmap "db-access" not found on the store-db pod and the store-backend initContainer never completes.

[dorlugasigal]

I get this as well,
anyway you can see that the db-admin is up, so both containers started (or at least tried) simultaneously

[chrisxfire]

Just stumbled upon this as well. This is an error in the task, I think.

[ash3rr]

Same error for me too. Woop wah.

[andreasbotsikas]

Thanks @nigelpoulton, it works as expected. Out of curiosity, during the exam, will the instructions give us the kubectl apply -f db-configmap.yml command or will we have to describe the pod, see the Error: configmap "db-access" not found error message and then search for the ConfigMap?

PS: I guess the back end is never supposed to run. I created the postgres service for the check-db to be able to resolve the postgres host and then ended up with ErrImageNeverPull status. Did I miss a step?

[ChrisProlls]

@andreasbotsikas same behavior on my side - the initContainer never reach the postgres server even when I successfully launch the postgres Pod.

[redbullhorns]

initContainer is failing to check if the postgres db is running on port 5432. Tried to change the host from postgres to the container name, db it is still failing. May be the solution is to create a service and the initContainer check if the postgres db is running through the service.