The tutorial guide Getting Started With Wildfly on OpenShift contains a few errors:

1. The line used to provision the PostgreSQL database uses

DATABASE_SERVICE_NAME=todos-db

instead of the correct name

DATABASE_SERVICE_NAME=todo-backend-db

The database is allocated for use by the next deployment in the example, todo-backend.

The helm chart for todo-backend contains a hard-coded reference to a secret called todo-backend-db containing a DATABASE_USER, DATABASE_PASSWORD and DATABASE_NAME which the PostgreSQL template deployment should produce. The template for postgresql-ephemeral generates such secret using the name DATABASE_SERVICE_NAME. 

When the typo is present, the deployment of the todo-backend Pods get stuck with a CreateContainerError and the deployment does not complete successfully. Not a great start for someone wanting to try out Wildfly!

2. The curl commands to access the todo-backend application deployment, as described in the tutorial, fail with the error:

curl: (60) SSL certificate problem: self-signed certificate in certificate chain
More details here: https://curl.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

This error can be avoided by adding the parameter --insecure, but it should not have to.

The same error applies to accessing the jaxrs-client example.