Extend API endpoints for Gateway component
Opened this issue · 0 comments
Short
We need new API endpoints in the networking components in order to register and manage new Gateway components.
Proposal
The upcoming gateway component will allow for external connectivity to the inside of the Oakestra network. We plan to allow this gateway component to attach at the two levels present - root and cluster. This will allow for encapsulation of network traffic, since inherently a gateway component attached to the root will or should be able to manage connections to the entirety of Oakestra deployed services. Gateways attached to a cluster orchestrator will or should be able to allow for connections to services deployed at the respective cluster.
In order to register and manage such gateways we need new API endpoints.
Ratio
This will allow for gateways to assign to the Oakestra network in order to allow for external connectivity.
Impact
Since we are planning to allow the component to attach to any orchestrator level, we will need the APIs from the root and cluster service managers to support the registration.
Status
Looking for feedback
Checklist
- Discussed
- Documented
- Implemented
- Tested