Closed elkh510 closed 4 years ago
duplicate of #769
problem resolves by adding this parameter
--pg-advertise-port string postgresql instance port from outside. Use it to expose port different than local port with a PAT networking config
https://github.com/sorintlab/stolon/blob/master/doc/commands/stolon-keeper.md
What happened: if istio sidecar injection enabled, unable to connect to stolon:
What you expected to happen: normal connecting to stolon How to reproduce it (as minimally and precisely as possible): 1) deploy istio 1.5.1 2) create namespace (exemple - stolon) 3) enable istio-injection (
kubectl label namespace stolon istio-injection=enabled
) 4) deploy stolon by helm chart 5) deploy pod with stolon client and try to connect to stolon serverAnything else we need to know?: tryed same configuration with postgres helm chart (without stolon) all work as expected
Environment: