cannot use built-in ingress with cert-manager

For some reason, cert-manager will only read a single TLS host when the `hosts` line is duplicated in the ingress resource. Kubernetes seems to handle it fine. 

https://github.com/coder/coder/blob/811a69f37173a688adf3880b545252f61fe747f7/helm/templates/ingress.yaml#L45-L50

I had to manually change the ingress to this for cert-manager to do both certificates.

```sh
 - hosts: 
     - coder.example.com
     - *.coder.example.com
```

Is this a quick fix on our end or should I report this with cert-manager?

	- hosts:
	- {{ .Values.coder.ingress.host \| quote }}
	secretName: {{ .Values.coder.ingress.tls.secretName \| quote}}
	{{- if .Values.coder.ingress.tls.wildcardSecretName }}
	- hosts:
	- {{ include "coder.ingressWildcardHost" . \| quote }}

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

cannot use built-in ingress with cert-manager #6634

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

cannot use built-in ingress with cert-manager #6634

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions