charts
charts copied to clipboard
Be a TLS enabled LoadBalancer
We're using drone as a LoadBalancer service with TLS enabled via the certs extraVolume. There are two problems with this.
- There is only one
ports
to be open via the service, and is hardcoded to be HTTP. TheservicePorts {}
map makesports
totally configurable. - The liveness probe is hardcoded to talk HTTP to the port HTTP, but with TLS enabled drone responds with a HTTP 307 to plan HTTP requests, causing the liveness probe to fail. I'm using the existence of a
certs
volume to decide if TLS is enabled, and if so do HTTPS liveness probes.
Sorry for the delay here.
I think this would be a nice feature to add. If you can resolve the conflicts, I will review. Thanks!