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.

Sign up for GitHub

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

Jump to bottom

Provision custom CA certificates into every container of the workspace pod #17407

Closed
tolusha opened this issue Jul 15, 2020 · 0 comments
Closed

Provision custom CA certificates into every container of the workspace pod #17407

tolusha opened this issue Jul 15, 2020 · 0 comments
Assignees
@mshaposhnik
Labels
area/che-server kind/task Internal things, technical debt, and to-do tasks to be performed. new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes severity/P1 Has a major impact to usage or development of the system.
Milestone
7.17

Comments

@tolusha
Copy link
Contributor

tolusha commented Jul 15, 2020

Is your task related to a problem? Please describe.

It is not possible to initialize Theia components when Eclipse Che is deployed behind proxy with custom CA certificate.
For instance cloning projects failed.

Describe the solution you'd like

Provision custom CA certificates into a workspace pod containers to reuse by Theia and their components.
All needed certificates are put in the configmap map (https://github.com/eclipse/che-operator/blob/fixdeploymentsinglehost/deploy/operator.yaml#L83)
TODO: put the name of this configmap into che configmap to use in che-server

Describe alternatives you've considered

All certificates already mounted in /public-certs in che-server container.
Copy them into workspace pod containers.

Additional context

https://issues.redhat.com/browse/CRW-1054
@tolusha tolusha added the kind/task Internal things, technical debt, and to-do tasks to be performed. label Jul 15, 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 Jul 15, 2020
@skabashnyuk skabashnyuk added area/che-server severity/P1 Has a major impact to 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 Jul 15, 2020
@tolusha tolusha mentioned this issue Jul 15, 2020
Merged
@skabashnyuk skabashnyuk added this to the 7.17 milestone Jul 16, 2020
@l0rd l0rd added the new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes label Jul 18, 2020
@tolusha tolusha mentioned this issue Jul 20, 2020
Closed
@mshaposhnik mshaposhnik mentioned this issue Jul 22, 2020
Merged
@tolusha tolusha mentioned this issue Jul 23, 2020
Merged
@mmorhun mmorhun mentioned this issue Aug 3, 2020
Closed
@tolusha tolusha mentioned this issue Aug 4, 2020
Closed
42 tasks
@ibuziuk ibuziuk mentioned this issue Aug 5, 2020
Closed
2 tasks
@tolusha tolusha mentioned this issue Aug 19, 2020
Closed
58 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mshaposhnik mshaposhnik

Labels
area/che-server kind/task Internal things, technical debt, and to-do tasks to be performed. new&noteworthy For new and/or noteworthy issues that deserve a blog post, new docs, or emphasis in release notes severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Milestone
7.17
Development

No branches or pull requests
5 participants
@l0rd @skabashnyuk @tolusha @mshaposhnik @che-bot