You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which image of the operator are you using? e.g. ghcr.io/zalando/postgres-operator:v1.14.0
Where do you run it - cloud or metal? Kubernetes or OpenShift? local k3d cluster
Are you running Postgres Operator in production? no
Type of issue? feature request
The master and replica load balancers both use the same port number, preventing them from running on the same host. Please provide a way to change the port number being used by each load balancer so we can run them on the same host if needed. This is especially needed for debugging/testing against a local cluster.
The text was updated successfully, but these errors were encountered:
Alternatively, provide a way to run internal load balancers (without a hostport). I just need a way to route the application (running inside the cluster) to the master or replicate databases.
The master and replica load balancers both use the same port number, preventing them from running on the same host. Please provide a way to change the port number being used by each load balancer so we can run them on the same host if needed. This is especially needed for debugging/testing against a local cluster.
The text was updated successfully, but these errors were encountered: