We have an 8 node cluster setup in AWS. Currently our application servers as well as our aerospike cluster is part of the same VPC but separate subnets. Our application servers use the private IP addresses of the aerospike instances in order to connect to them.
We are planning to upgrade our aerospike cluster from 188.8.131.52 to 184.108.40.206. Instead of going for an inplace upgrade, we are planning to spin up a parallel upgraded cluster and eventually move traffic into the new cluster. We had a question regarding a seamless traffic shifting from the old to the new cluster. With the current setup and upgrade procedure, a traffic shifting as you might have guessed would involve changing the private IPs in the application server configurations and doing a rolling update/deployment.
We would want a seamless upgrade to be one in which no application configuration changes are required. This would mean the application servers still point to the original endpoint and we are able to change the servers behind those endpoints. As far as best practices are considered, what is the ideal way of designing the infra with aerospike for seamless upgrades(major version upgrades as well as patch version upgrades)!