-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
Kessel | External Cluster Access [UI]
-
Product / Portfolio Work
-
False
-
-
False
-
Unset
-
To Do
-
CRCPLAN-356 - Management Fabric | M5 - Full Workspace and Access Mgmt. for Early Adopters
-
100% To Do, 0% In Progress, 0% Done
-
-
-
Review the CRCPLAN parent feature for additional context, including the feature overview, goals, user stories and use cases, acceptance criteria, designs, dependencies, risks, assumptions, pending questions and documentation callouts.
Summary and goal
The HCC UI, RHSM, OCM and other Management Fabric adopters who are not deployed in the same cluster as the core Management Fabric services (primarily Kessel Inventory) will need to access Kessel through console.redhat.com vs internally via cluster services directly as other HCC and Insights services do. Work is needed across multiple services in order to enable and secure this functionality.
Acceptance Criteria
These conditions must be met for the epic to be considered complete. This provides a detailed definition of scope and the expected outcomes, written from a user's point of view.
- As an HCC UI experience engineer, I should be able to make HTTP requests from the front-end to Kessel services externally on console.redhat.com using a user JWT from RHSSO.
Checklist
Checklist Item | Required | Notes or Comments |
---|---|---|
Workstream or external team dependencies? | Y / N | |
ADR Required?
|
Y / N | |
Testing plans
|
Y / N | |
Known dependencies?
|
Y / N |
Open Questions
Do any of these external services require bootstrapping without first visiting console?
- e.g. is subs inventory still available outside console?