Where 192.168.204.1 is the active controller's floating IP address. This creates a socket connecting the pod to the currently active controller. After performing a swact, this socket becomes invalid, because it still points to the now inactive controller, and that is why the broken pipe error happens.
The armada-api pod, which runs helm 2, goes up with the following command when starting the tiller container:
tiller --storage=sql --sql-dialect= postgres --sql-connectio n-string= postgresql: //admin- helmv2: PASSWORD@ 192.168. 204.1:5432/ helmv2? sslmode= disable -listen :24134 -probe-listen :24135 -logtostderr -v 5
Where 192.168.204.1 is the active controller's floating IP address. This creates a socket connecting the pod to the currently active controller. After performing a swact, this socket becomes invalid, because it still points to the now inactive controller, and that is why the broken pipe error happens.