-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Osf 3893 release 0.9.0 #4247
Osf 3893 release 0.9.0 #4247
Conversation
- upgrade instructions - version bump - clarifictions/small fixes
db934a9
to
73f4f8c
Compare
73f4f8c
to
25ece59
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Not sure whether we need @geropl's review as it's mostly deletions and docs.
@@ -7,6 +7,10 @@ version: | |||
hostname: localhost | |||
certificatesSecret: | |||
secretName: https-certificates | |||
certName: cert.pem |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like a step backwards from the TLS secret type we're moving to
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like a step backwards from the TLS secret type we're moving to
The goal here is to still support the certificates that come out of letsencrypt right away, by default. Otherwise we'd need to tell Self-Hosted users to do yet another step: https://www.gitpod.io/docs/self-hosted/latest/install/configure-ingress#using-lets-encrypt-to-generate-https-certificates
Closing out due to age and conflicts. |
This is pretty much a cherry pick of the first commits from this PR #3925