Connections are not restarted when there is a failover

Please, answer some short questions which should help us to understand your problem / question better?

• Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.8.2
• Where do you run it - cloud or metal? Kubernetes or OpenShift? GKE
• Are you running Postgres Operator in production? Yes
• Type of issue? [Bug report, question, feature request, etc.] Question/Feature request?

Hi all, hope you are well.
Every time that something happens with the master node, the cluster fails over flawlessly to a replica node. However, the issue I'm experiencing is that my applications keep trying to write queries to the former master node (now replica) after the failover.
My question is: is there anywhere in the configs where I can set the DB to restart/deny current connections whenever there is a failover?
Just checking if there is a possibility to do so, otherwise, we'll have to change the way our applications connect to the database.

No file or test is named. Start by reviewing the Postgres Operator's failover and connection-handling behavior, then determine whether an existing configuration controls connections to the former master. Done should be a documented supported configuration or a clearly scoped implementation decision.