Adding subdomain/wildcard trough helm

Is there an example of how I can add subdomain support with HelmChart?
I've added:

ingress: 
 ...
 wildcardHost: "*.domain.com"
 tls: 
  wildcardSecretName: wildcard-tls

ingress: 
 ...
 wildcardHost: "*.domain.com"
 tls: 
  wildcardSecretName: wildcard-tls

ingress: 
 ...
 wildcardHost: "*.domain.com"
 tls: 
  wildcardSecretName: wildcard-tls

ingress: 
 ...
 wildcardHost: "*.domain.com"
 tls: 
  wildcardSecretName: wildcard-tls

But seems like the tls is failing

Codercord•8/6/23, 2:38 AM

<#1137575332287881286>

**Category**

Other

**Product**

Coder OSS (v2)

**Platform**

Linux

Logs

Please post any relevant logs/error messages.

Elio•8/6/23, 4:27 AM

Did you also configure the required environment variables?

EElio Did you also configure the required environment variables?

HoXsanOP•8/6/23, 2:29 PM

Yes, the title might be misleading, I am looking for a way to make TLS work with subdomain/wildcard

Elio•8/6/23, 5:00 PM

Ah so you have configured the subdomain but TLS is not working correctly?

HoXsanOP•8/6/23, 5:39 PM

Yes

Elio•8/6/23, 5:57 PM

What's the issue? The secret doesn't work? Your cert is invalid?

EElio What's the issue? The secret doesn't work? Your cert is invalid?

HoXsanOP•8/6/23, 7:20 PM

Yes, its in pending state.

Elio•8/6/23, 8:46 PM

I'm not sure what that means

nowai_david•8/6/23, 10:45 PM

@HoXsan You will want to debug the TLS certificate since that is the responsibility of your certificate provider. So I would start by inspecting the certificate and then working backwards for orders and then challenges. It sounds like a root issue lying with your issuer.

Nnowai_david <@319138840092606465> You will want to debug the TLS certificate since that is t...

HoXsanOP•8/7/23, 2:24 PM

Thanks, I'll try to debug it. But wasn't able to find anything useful :/

HoXsanOP•8/7/23, 7:31 PM

Hmm, when I use: wildcardHost: *.domain.comwildcardHost: *.domain.com the certificate wont work. But when I use domain.comdomain.com it works. Something is odd with the wildcard

Elio•8/7/23, 7:55 PM

Is you cert set up as a wildcard cert?

HoXsanOP•8/7/23, 8:11 PM

Yea it should be. I get this error within Certificate: Existing issued Secret is not up to date for spec: [spec.commonName spec.dnsNames]Existing issued Secret is not up to date for spec: [spec.commonName spec.dnsNames]

HoXsanOP•8/7/23, 8:11 PM

Looking it up now

HoXsanOP•8/7/23, 9:10 PM

not sure, but can it be cause of http01 resolver in the issuer?

Elio•8/8/23, 1:34 AM

I'm not sure tbh, sounds like maybe the secret is configured wrong?