Description of problem: It's a little hard for new users to add workloads to project since no links to any sources provided on projects workloads page Version-Release number of selected component (if applicable): 4.2.0-0.nightly-2019-07-31-162901 How reproducible: Always Steps to Reproduce: 1. A new user without any projects logins to console 2. Create a test project by clicking `Create Project` on /k8s/cluster/projects page, after project is successfully created, user is taken to project details page 3. Click on Workloads tab Actual results: 3. It shows "No Workloads Found" because this is a new project and user didn't add any applications. User can't add workloads directly neither via DeployImage, Browse Catalog nor Import YAML Expected results: 3. It will be much better if we can add some links to Developer Console where user can add applications easily. Currently when user wants to add workloads vai Deploy Image, Browse Catalog etc, he has to switch to Developer console manually, but for new users he may don't know about Developer Console, also don't know how to switch to Developer Console. Some links to Deploy Images, Browse Catalog are good too. `Import YAML` function is a plus too Additional info: in 4.1, we give user some options (Deploy Image, Import YAML, Browse Catalog) where user can add workloads quickly
This is an intentional design decision to have the workloads tab empty state be truly empty. See http://openshift.github.io/openshift-origin-design/web-console/future-openshift/dashboards/dashboards. Colleen, care to chime in here?
1. User create a new project 2. On Project Workloads page, it will show No Workloads Found. Import YAML or add other content to your project. 3. Clicking on 'Import YAML' will open YAML editor, user can create resources via YAML 4. Clicking on 'add other content' will redirect user to Add page where user can add workloads to project very easily Thanks, this is very helpful. Moving to VERIFIED 4.2.0-0.nightly-2019-08-14-211610
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. https://access.redhat.com/errata/RHBA-2019:2922