Please fill in the following information:

Issue description

 Description:  do288-4.14 - ch02s07 - Lab: Deploying Simple Applications

The error 'could not connect to the database:error: password authentication failed for user "developer".' isn't descriptive enough to suggest to your user's 'what they need to fix' and without more context or information about the application being deployed. Because the step 7 is so far away from step 3 and 4, panic can set in (one stops reading the instructions and starts debugging). In short some indication to the user that the application isn't intended to deploy correctly would be nice (on step 3). 

Step 6 in the review isn't necessary; you could just edit the deployment or use `oc set env` to supply the proper environment variable DB_PASSWORD=test to the application; it is faster and a more reasonable and realistic solution that more closely mimic what one might do in the real world. 

Add to the table the application endpoint (todos) and the a sample data supplement ('{ "task": "example task" }') so that proper context for how to interact with the application is supplied/provided. (for step 8). Doing so helps users understand what is happening with step 8.  

Steps to reproduce:

Workaround:

Expected result: