Support OpenShift global proxy configuration and trusted certificate bundle when DevWorkspace is enabled #20386
Labels
area/dashboard
kind/enhancement
A feature request - must adhere to the feature request template.
severity/P1
Has a major impact to usage or development of the system.
sprint/next
Milestone
Comments
l0rd
added
kind/enhancement
|
@metlos is this issue covered by eclipse-che/che-operator#1027? |
|
Yes, this should theoretically be handled by eclipse-che/che-operator#1027. It copies the configuration gathered by che-operator during che-server deployment time also into the namespaces of devworkspaces so that DWO can inject it into devworkspace pods. |
|
This is implemented in eclipse-che/che-operator#1027. |
|
closed for Che 7.37 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your enhancement related to a problem? Please describe
That's related to clusters that use a proxy or other services that use a certificate signed by an untrusted CA.
Describe the solution you'd like
OpenShift has a mechanism to distribute the certificates bundle and we support it when the che-server is used to start workspaces.
We should support it in the DevWorkspace scenario too.
Describe alternatives you've considered
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: