Open gitreich opened 2 months ago
Thanks for starting this! I was thinking we'd want to actually have the secret be created as part of the Helm chart, from the key and cert files themselves, eg something like:
...
tls: true
tlsCert: <path/to/cert>
tlsKey: <path/to/key>
and then adding a Secret definition in secrets.yaml that creates the secret from these files. But, I think that does mean the cert and key files need to be in the same directory as the chart, which may be less than ideal...
I guess providing a separate Secret might be easy enough, given that the user is responsible for managing it.
For authsign, I think it'll need to be updated, since it doesn't really support working with external certs or k8s secrets at the moment.
For manually adding a secret for a tls of another authority then Let's Encrypt See https://github.com/webrecorder/browsertrix/issues/2077 Fix for frontend&backend ingress Still open: auth-signer is not using the same secret