Description of problem: Users are directed to the topology view for the 'default' namespaces (on the developer console), vs being directed to a namespace they own, or some other 'overview'/'landing' page.
Version-Release number of selected component (if applicable):
> Kubernetes Version: v1.16.2
> API Server: https://api.us-east-2.starter.openshift-online.com:6443
How reproducible: 100%
Steps to Reproduce:
1. Navigate to https://console-openshift-console.apps.CLUSTER.DOMAIN/
- In this case OpenShift Starter
2. I will take you to the '/topology/ns/default' context.
> Restricted Access
> You don't have access to this section due to cluster policy.
> Danger alert:Error details
deploymentconfigs.apps.openshift.io is forbidden: User "USER" cannot list resource "deploymentconfigs" in API group "apps.openshift.io" in the namespace "default"
The first thing a user sees, with the development console should not be an error (Restricted Access).
There is a change in 4.5 where the user will no longer encounter the error `deploymentconfigs.apps.openshift.io is forbidden: User "USER" cannot list resource "deploymentconfigs" in API group "apps.openshift.io" in the namespace "default"`
However the user is still redirected to the default namespace whether they have access or not.
Will look to change the default namespace to something else for 4.5 re-evaluate the first experience flows in 4.6.
A change was made to now default new users into `all projects` instead of the 'default' namespace which they may not have access to. A new user will no longer see an error the first time they visit the dev perspective.
In future releases we will continue to improve on the initial flows for new users.
I have validated the bugzilla on:
Browser: Google Chrome Version 81.0.4044.129
Marking this as verified.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.