Deployment fails when kubeadmin is the only user. That happens whenever someone wants to try CRW on a fresh OpenShift installation. This is a common scenario for users that want to test CRW and if they have a bad first experience we are going to lose them.

We should either consider kubeadmin as a valid CRW user (if Keycloak allows using it as a valid OAuth identity) or fall-back to openShiftoAuth: false.

Solution chosen was to fall back to openShiftoAuth: false if no oauth users present, so deployment succeeds and the CRW default admin:admin user can then be used to create a workspace.