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

Mount CA cert secret in ws-daemon, server and image-builder #9078

Closed
Tracked by #9074
csweichel opened this issue Apr 1, 2022 · 0 comments · Fixed by #9239
Closed
Tracked by #9074

Mount CA cert secret in ws-daemon, server and image-builder #9078

csweichel opened this issue Apr 1, 2022 · 0 comments · Fixed by #9239
Labels
type: feature request New feature or request

Comments

@csweichel
Copy link
Contributor

csweichel commented Apr 1, 2022

When Gitpod is running using "self-signed" certs this can mean one of four things:

  • the SCM Gitpod will need to talk to uses certs signed by a custom CA
  • the Docker registry Gitpod will need to talk to uses certs signed by a custom CA
  • Gitpod itself will serve its content using certs signed by a custom CA
  • we need to support a custom CA cert in workspaces to access other services

In all those cases we need to mount the CA certs in /etc/ssl/certs/somefilename.crt in the following container:

  • ws-daemon
  • image-builder
  • server

In case of server we also need to set the NODE_EXTRA_CA_CERTS env var to point to /etc/ssl/certs/somefilename.crt. In case of the Go components placing the file is enough (if it exists prior to the start of those services - which it does in case of Kubernetes).

Note: we must not mount the secret into /etc/ssl/certs directly, as that would replace the other root CA certs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature request New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant