CONSOLE-2892: Allow dynamic plugins to proxy to services on the cluster#915
Conversation
|
cc @jamestalton |
| After that plugin can make request to the console endpoint, which will | ||
| proxy the request to the dependent service. Plugin's request shall use | ||
| following console's endpoint: | ||
| `/api/plugin-proxy/<dependent-service-name>/<request-path>` |
There was a problem hiding this comment.
This path isn't guaranteed to be unique. We should include the service namespace and port in the path.
There was a problem hiding this comment.
Maybe
| `/api/plugin-proxy/<dependent-service-name>/<request-path>` | |
| `/api/proxy/namespace/<service-namespace>/service/<service-name>:<port-number>/<request-path>?<optional-query-parameters>` |
I'd suggest providing a concrete example URL and what service URL that it maps to.
There was a problem hiding this comment.
Another option is to use e.g. /api/proxy/<plugin-name>/<service-name>/<request-path> since there can be only one proxy service with the given name for the given ConsolePlugin resource manifest.
There was a problem hiding this comment.
Service name is not unique... A plugin can proxy to two services with the same name in different namespaces, or the same service, but different ports.
|
@spadgett @vojtechszocs PTAL |
|
Thanks for additional comments! I've addressed them 👍 |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: spadgett The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
First draft of the proposed feature for allowing dynamic plugins to proxy to services on the cluster.
Story: https://issues.redhat.com/browse/CONSOLE-2892
/assign @spadgett @vojtechszocs @christianvogt