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
Add configurable secret names for wildcard instances (#73)
Previously, all instances - regardless of whether they contain wildcards or not - were using the same hard-coded `ws-cert-secret` TLS secret name. This results in the inability to use a preconfigured certificate only for the wildcard routes but keep the regular process for non-wildcard routes in place.
This PR introduces an optional field `ingress.allWildcardSecretNames` that accepts a wildcardPattern->secretName mapping and configures the ingress to use the configured secret for the wildcard host.
Making sure that no existing functionality is broken, the changes also make sure that:
- ingress.allWildcardSecretNames does not introduce new routes. Only routes that were already
configured via hosts.allWildcardInstances can be modified with a new secretName.
- ingress.allWildcardSecretNames is optional and any wildcard-instance will use the `ws-cert-secret` by default.
This also allows partial changes to some routes' certs.
Co-authored-by: Lucas Koehler <[email protected]>
Copy file name to clipboardExpand all lines: charts/theia-cloud/README.md
+1
Original file line number
Diff line number
Diff line change
@@ -33,6 +33,7 @@ A Helm chart for Theia Cloud
33
33
| imagePullPolicy | string |`"Always"`| The default imagePullPolicy for containers of theia cloud. Can be overridden for individual components by specifying the imagePullPolicy variable there. Possible values: - Always - IfNotPresent - Never |
34
34
| ingress | object | (see details below) | Values to influence the ingresses |
35
35
| ingress.addTLSSecretName | bool |`true`| whether the default Theia Cloud tls secret names should be used. If false no tls secret name will be set on the ingress only needed when ingress.tls == true |
36
+
| ingress.allWildcardSecretNames | object |`{}`| All additional wildcard hostnames and the respective TLS secret names. Use this for wildcard hostnames that should use a TLS certificate with a `secretName` different from the default one. Only accepts wildcard hostnames that are configured in `hosts.allWildcardInstances`. |
36
37
| ingress.certManagerAnnotations | bool |`true`| When set to true the cert-manager.io annotations will be set. Only used when ingress.addTLSSecretName === true When false certificate management is handled outside of Theia Cloud. |
37
38
| ingress.clusterIssuer | string |`"letsencrypt-prod"`| The cluster issuer to use Only needed when ingress.certManagerAnnotations is true |
38
39
| ingress.instanceName | string |`"theia-cloud-demo-ws-ingress"`| The name of the ingress which will be updated to publish new theia application. If this is not existing it will be created. You may chose to set the ingress up yourself and point Theia Cloud to the ingress via the name |
0 commit comments