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
On our production platform, we're using a purchased wildcard TLS certificate for *.app.uffizzi.com. For customers requiring additional subdomains, we must instead configure cert-manager to provision a new certificate for all subdomains.
Child of https://github.com/UffizziCloud/uffizzi_platform/issues/239#issuecomment-1244492724
On our production platform, we're using a purchased wildcard TLS certificate for
*.app.uffizzi.com
. For customers requiring additional subdomains, we must instead configurecert-manager
to provision a new certificate for all subdomains.UX described in related ticket UffizziCloud/uffizzi#257
When a customer specifies any number of additional subdomains, our controller should add to the deployment's
Ingress
resource, including:cert-manager.io/cluster-issuer: letsencrypt
.rules
for each subdomain (wildcard would probably work here as well.)tls.hosts
.tls.secretName
(can be same as "root" hostname.)Example result
Ingress
in YAML:Note that this change is almost, but not quite, the opposite of changes made earlier this year to enable using the single wildcard certificate. Do not revert these changes, do NOT use the
CERT_MANAGER_CLUSTER_ISSUER
environment variable as-is. https://gitlab.com/dualbootpartners/idyl/uffizzi_controller/-/merge_requests/178/diffsThe text was updated successfully, but these errors were encountered: