-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
CAPS | Expose Over East-West Gateway
-
Product / Portfolio Work
-
False
-
-
False
-
Unset
-
To Do
-
-
-
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 goal of this epic is to expose the ext_authz API of CAPS via the east-west gateway. This is necessary to enable other gateways, such as those in the Pulp clusters, to consume the gateway service functionality.
Acceptance Criteria
- The ext_authz API is reachable and functional from outside of hcc clusters via the cross-cluster gateway
- The east-west gateway is configured to correctly route traffic to the gateway service's ext_authz API
- CAPS can be consumed by gateways deployed in external environments, such as the Pulp clusters (assuming appropriate authorization policy is in place)
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
- depends on
-
RHCLOUD-42363 Set up East-West Gateway
-
- Refinement
-
-
RHCLOUD-42365 CAPS | Initial implementation
-
- Refinement
-