You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We want users to be able to use self-signed certs in their self-hosted Gitpod installation
Context
ℹ️ Defining Self-Signed Certs
There are many ways to define self-signed certs, but this is the definition we are using: self-singed certs are any certs that are not signed by a public certificate authority (ca) that is already known to linux, i.e. the CA’s certs are already shipped with the linux build.
Some users want to use components or run in environments that require self-signed certs. We want to allow for this.
--> This is an epic for #8559 . We think this will require further collaboration between teams, which is why we want to bring it to the epic level.
Value
This unlocks a new type of user / customer for us which previously was unable to use self-hosted Gitpod due to the certificates they used. Further, it facilitates installing Gitpod on your local machine.
Acceptance Criteria
Self-signed certs can be propagated into:
server-pod
ws-daemon container
workspace container
on the node to use for containerd
Image builder (assuming the registry it talks to is using self signed certs)
We have basic documentation in place and this feature is tested with at least one user.
Measurement
We run nightly tests that use self-signed certs and these run successfully
At least one customer has successfully used self-signed certs in their installation
Complexities
On GKE you cannot allow containerd to trust other certificates without restarting containerd. This hinders us from having self-signed certs on GKE right now.
Summary
We want users to be able to use self-signed certs in their self-hosted Gitpod installation
Context
ℹ️ Defining Self-Signed Certs
There are many ways to define self-signed certs, but this is the definition we are using: self-singed certs are any certs that are not signed by a public certificate authority (ca) that is already known to linux, i.e. the CA’s certs are already shipped with the linux build.
Some users want to use components or run in environments that require self-signed certs. We want to allow for this.
--> This is an epic for #8559 . We think this will require further collaboration between teams, which is why we want to bring it to the epic level.
Value
Acceptance Criteria
Self-signed certs can be propagated into:
We have basic documentation in place and this feature is tested with at least one user.
Measurement
Complexities
On GKE you cannot allow containerd to trust other certificates without restarting containerd. This hinders us from having self-signed certs on GKE right now.
Child Issues
The text was updated successfully, but these errors were encountered: