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

[devworkspace] add an ability to configure trust store e.g. for plugin registry with self-signed certs #17898

Closed
Tracked by #19538
sleshchenko opened this issue Sep 17, 2020 · 3 comments
Labels
area/devworkspace-operator engine/devworkspace Issues related to Che configured to use the devworkspace controller as workspace engine. kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P3 Lower priority than a P2. Optional work that might get done, or not. See also help wanted issues.

Comments

@sleshchenko
Copy link
Member

Is your task related to a problem? Please describe.

Add an ability to configure the trust store e.g. for plugin registry with self-signed certs.

Describe the solution you'd like

It's possible to configure CA certs for plugin brokering at least.
Later we may need to propagate self-signed CAs to devworkspaces but I would like to separate it.

@sleshchenko sleshchenko added kind/task Internal things, technical debt, and to-do tasks to be performed. engine/devworkspace Issues related to Che configured to use the devworkspace controller as workspace engine. labels Sep 17, 2020
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Sep 17, 2020
@benoitf
Copy link
Contributor

benoitf commented Sep 17, 2020

also I could live with an insecure flag as well

@sleshchenko
Copy link
Member Author

The agreement we got during planning - the configuring CA could differ depending on the future plan regards plugin registry deployment, should it be a part of devworkspace controller or not.
At this point, it does not have a big priority (configuring and propagated CA), but we're going to introduce configuration flag to enable insecure connections to the configured plugin registry.

@sleshchenko sleshchenko added severity/P2 Has a minor but important impact to the usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Sep 18, 2020
@sleshchenko sleshchenko added severity/P3 Lower priority than a P2. Optional work that might get done, or not. See also help wanted issues. and removed severity/P2 Has a minor but important impact to the usage or development of the system. labels Sep 30, 2020
@l0rd l0rd added this to the DevWorkspace Integration - STEP2 milestone Mar 5, 2021
@l0rd l0rd removed this from the DevWorkspace Integration - STEP2 milestone Apr 8, 2021
@l0rd l0rd mentioned this issue Apr 8, 2021
29 tasks
@l0rd
Copy link
Contributor

l0rd commented Sep 8, 2021

After discussion at this week dw cabal we agreed that this should close this as won't fix.

@l0rd l0rd closed this as completed Sep 8, 2021
@l0rd l0rd removed this from the DevWorkspace Integration - STEP3 milestone Sep 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/devworkspace-operator engine/devworkspace Issues related to Che configured to use the devworkspace controller as workspace engine. kind/task Internal things, technical debt, and to-do tasks to be performed. severity/P3 Lower priority than a P2. Optional work that might get done, or not. See also help wanted issues.
Projects
None yet
Development

No branches or pull requests

4 participants