the ability to use a k8s Ingress object to connect to the deployed pgAdmin instance using a persistent static IP address (and therefore the ability to point a DNS record at the instance);
the ability to use a cert-manager ClusterIssuer to automatically provision a TLS certificate for said Ingress object, such that the Ingress will then route HTTPS as well as HTTP traffic.
Note that, as is, pgAdmin will still think it's receiving HTTP traffic, it will sometimes create links or redirects that hardcode http:// as their schema, switching the client away from HTTPS when these links/redirects are followed. Smart IngressControllers (e.g. ingress-nginx) may automatically fix these up when the response passes through them. Dumber IngressControllers (e.g. the load balancer of Google Cloud) won't.
This PR adds two things:
Ingress
object to connect to the deployed pgAdmin instance using a persistent static IP address (and therefore the ability to point a DNS record at the instance);Ingress
object, such that the Ingress will then route HTTPS as well as HTTP traffic.Note that, as is,
pgAdmin
will still think it's receiving HTTP traffic, it will sometimes create links or redirects that hardcodehttp://
as their schema, switching the client away from HTTPS when these links/redirects are followed. SmartIngressController
s (e.g. ingress-nginx) may automatically fix these up when the response passes through them. DumberIngressController
s (e.g. the load balancer of Google Cloud) won't.