Please vote on this issue by adding a :thumbsup: reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Tell us about the feature
In conversations with users, we learnt about the use case, where it is desired to add more nodes into the existing PXC cluster instead of doing an async replication between two distinct clusters.
For example, one user was doing blue-green deployments when upgrading k8s cluster. For stateless apps, it was easy to deploy some Pods in the new k8s cluster and partially route the traffic.
Whereas for PXC the only option is having async replication between two distinct clusters, vs just adding one more node.
Community Note
Tell us about the feature
In conversations with users, we learnt about the use case, where it is desired to add more nodes into the existing PXC cluster instead of doing an async replication between two distinct clusters.
For example, one user was doing blue-green deployments when upgrading k8s cluster. For stateless apps, it was easy to deploy some Pods in the new k8s cluster and partially route the traffic.
Whereas for PXC the only option is having async replication between two distinct clusters, vs just adding one more node.
Similar to what we do in MongoDB, where we allow users to expand the replica set with externalNodes: [https://docs.percona.com/percona-operator-for-mongodb/replication.html]
Link to JIRA