Problem:

Brokers, Channels & Event Sources are not easily accessible in the Admin perspective, and are only accessible via Search.

Exploration Results

1. GA feature, thus should be properly documented
2. GA feature, thus need to provide enablement
3. Include in what's new RHD blog and consider for improved usability blog

• Step 1 - Empathize
• Step 2 - Define
• Step 3 - Ideate

Exploration recording

Acceptance Criteria

As an admin, I want...

1. a single Serverless area in the Admin navigation, containing 2 pages: Eventing & Serving
2. a tabbed page representing Serving which includes Services, Revisions & Routes
3. a tabbed page representing Eventing which includes Event Sources, Brokers & Channels
4. the ability to filter by type when looking at the list of Event Sources
5. the ability to filter by type when looking at the list of Channels
6. the ability to see event sources status when looking at the list of event sources wrt conditions status (this include sink Provided) and ready state
7. the ability to see channels/brokers status when looking at the list of these wrt conditions status and ready state
8. see associated Triggers when looking at Broker details
9. see associated Subscriptions when looking at Channel details
10. see associated filters when looking at Trigger details

Design Artifacts

tbd

Slack Channel

#tmp-odc-serverless on CoreOS Slack Instance

Notes

tbd