Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

An admin should be able to specify CA certificates that need to be trusted on devfile v2 based workspaces #20387

Closed
l0rd opened this issue Aug 31, 2021 · 4 comments
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

Comments

@l0rd
Copy link
Contributor

l0rd commented Aug 31, 2021

Is your enhancement related to a problem? Please describe

This is something that we do support for devfile v1 based workspaces but not for v2.

Describe the solution you'd like

Inject the certificates bundle on devworkspaces.

Describe alternatives you've considered

No response

Additional context

No response

@l0rd l0rd added kind/enhancement A feature request - must adhere to the feature request template. area/che-server area/dashboard severity/P1 Has a major impact to usage or development of the system. labels Aug 31, 2021
@l0rd l0rd mentioned this issue Aug 31, 2021
29 tasks
@skabashnyuk
Copy link
Contributor

@metlos is this issue covered by eclipse-che/che-operator#1027?

@metlos
Copy link
Contributor

metlos commented Sep 22, 2021

We now sync the ca-certs-merged that che-operator gathers into the devworkspace namespaces and mark it to be mounted into the devworkspace pods by DWO. @tolusha is that enough to implement what this issue asks for?

@tolusha
Copy link
Contributor

tolusha commented Sep 22, 2021

@metlos
I believe yes.

@metlos
Copy link
Contributor

metlos commented Sep 23, 2021

Closing as this should now be implemented.

@metlos metlos closed this as completed Sep 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

No branches or pull requests

4 participants