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
I'm in the process of installing PostgreSQL using the cloudnative-pg operator, which has been quite straightforward and trouble-free.
Now, I'm looking to expose PostgreSQL port 5432 to the public internet. Although I understand the risks associated with port exposure, in my scenario, it's a development system and PostgreSQL needs to be accessible.
To accomplish this, I need to open TCP port 5432 in the Ingress controller. This can be achieved seamlessly by defining custom nginx-values, as shown below:
Upon applying these settings, a new port definition is added to the nginx-ingress controller, along with a corresponding service definition in the Hetzner load balancer.
However, a challenge arises because all three service definitions (for http, https, and 5432) in the load balancer have the "use proxyprotocol" flag enabled due to the line:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
I'm in the process of installing PostgreSQL using the cloudnative-pg operator, which has been quite straightforward and trouble-free.
Now, I'm looking to expose PostgreSQL port 5432 to the public internet. Although I understand the risks associated with port exposure, in my scenario, it's a development system and PostgreSQL needs to be accessible.
To accomplish this, I need to open TCP port 5432 in the Ingress controller. This can be achieved seamlessly by defining custom nginx-values, as shown below:
Upon applying these settings, a new port definition is added to the nginx-ingress controller, along with a corresponding service definition in the Hetzner load balancer.
However, a challenge arises because all three service definitions (for http, https, and 5432) in the load balancer have the "use proxyprotocol" flag enabled due to the line:
"load-balancer.hetzner.cloud/uses-proxyprotocol": "true"
Since PostgreSQL doesn't support the proxy protocol, it needs to be disabled specifically for the load balancer service on port 5432.
My question is: Is it possible to configure "load-balancer.hetzner.cloud/uses-proxyprotocol": "true/false" per load-balancer service?
Thanks
Beta Was this translation helpful? Give feedback.
All reactions