feat(load-balancer): support for multiple domains in certificate(s)

[carstenblt]

Is it possible to assign multiple certificates to a load balancer?

I was expecting

load-balancer.hetzner.cloud/http-managed-certificate-domains: '*.domain1.com,*.domain2.com'

to work but it doesn't.

[github-actions]

This issue has been marked as stale because it has not had recent activity. The bot will close the issue if no further action occurs.

[timelapse2132]

We would also need this.

I hope this is not considered issue hijacking but I would like to explain our use case for this feature:
Currently we have a cluster with many different domains and cert-manager. LB has proxy protocol enabled, cert-manager therefore only works if we set load-balancer.hetzner.cloud/hostname on the ingress service object but this prevents us from adding more than one domain. Switching the challenge method is also not an idea because the same issue would occur if we try to access any domain pointing to the lb from within the cluster (Like in angular SSR from frontend pods).

What is recommended in this case? Is there any way to get ip address information without using proxy protocol (like headers set on the LB for example).

[github-actions]

This issue has been marked as stale because it has not had recent activity. The bot will close the issue if no further action occurs.

[rwojsznis]

If you're coming from search here - after hours of trial and error I kinda give up on managed certificates functionality - please see also this comment

went with cert-manager route and everything just work (using hetzner LB + Cloudflare + cert-manager dns01 challange combo)

[github-actions]

This issue has been marked as stale because it has not had recent activity. The bot will close the issue if no further action occurs.

[apricote]

Quick question: Would you need one certificate per domain or are multiple domains in one certificate fine? (Through Subject Alternative Name)

[carstenblt]

that would be finde for me