matslindh commented on issue #437:
URL: https://github.com/apache/solr-operator/issues/437#issuecomment-1124727164
It's fairly simple; it's a regular `tls` section in the ingress entry, but
without a reference to the secret. From another existing ingress:
```yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: <ingressname>
namespace: <namespace>
spec:
ingressClassName: nginx
tls:
- hosts:
- <hostname>
rules:
- host: <hostname>
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: <servicename>
port:
number: 8080
```
The relevant part is the `tls` section:
```yaml
tls:
- hosts:
- <hostname>
```
.. in other ingress entries you'd have `secretName: ingress-demo-tls`
together with the hostname as well, but since this has been configured as the
default cert on the ingress controller instead (with a wildcard certificate),
there isn't a need to provide a secret for this particular tls entry.
The nginx controller uses `default-ssl-certificate=namespace/secret-name` to
allow this to be configured on a controller basis.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org
