Replace the API service extension for the UCP with port forwarding #7944
Labels
maintenance
Issue is a non-user-facing task like updating tests, improving automation, etc..
triaged
This issue has been reviewed and triaged
Area for Improvement
Replace the UCP API server extension with port forwarding to the control plane. This would involve removing the integration with the API service and replacing it with a port forward rule, plus invoking the existing Kubernetes authentication. The CLI logic would create/teardown the port forwarding as needed.
The overall benefit will be scalability due to the removal of the Radius dependence on the API service.
An example of this approach is in Argo CD: https://github.com/argoproj/argo-cd/blob/master/pkg/apiclient/apiclient.go#L206
See also this issue comment.
This issue will require design.
Observed behavior
No response
Desired behavior
Update the CLI to use the port forwarding mechanism rather than communicating through the server extension.
Proposed Fix
This change would require a small design and approval.
rad Version
any
Operating system
No response
Additional context
No response
Would you like to support us?
AB#13216
The text was updated successfully, but these errors were encountered: