cockroachdb chart: enabling TLS and the ingress leads to a redirect loop for the UI ingress.

Dear maintainers,

with the TLS mode enabled, the WebUI ingress leads to a redirect loop in my demo setup. The ingress itself looks correct, but I only get a 307 redirect back:

```
$ curl -Ik https://cockroachdb.192.168.121.102.sslip.io
HTTP/2 307
content-type: text/html; charset=utf-8
date: Mon, 22 Jun 2026 11:43:01 GMT
location: https://cockroachdb.192.168.121.102.sslip.io/
$
```

As you can see, the `location` points to the same URL that was being curl'ed.

Any ideas what I did wrong (or what is missing in the ingress definition)?

Host is k3s single node with Traefik.

Kind Regards,
Johannes

Reproduce the redirect loop using the cockroachdb chart with TLS and the WebUI ingress enabled on k3s with Traefik. Start by inspecting the chart's TLS and ingress configuration, then compare the generated ingress definition with the curl response. Done means the UI ingress no longer redirects back to the same HTTPS URL, or the missing configuration is clearly identified.

Written by the indexing model from the issue text.