Kubegres is a Kubernetes operator allowing to deploy one or many clusters of PostgreSql instances and manage databases replication, failover and backup.
When I disable failover, whether by stopping the primary pod using pg_ctl (simulating a crash) or deleting the pod, a new pod will be created (or restarted) with the same name.
However, when testing the replica pod with the same operation, regardless of the method used, a new pod with a different name is restarted each time, and eventually, a new PVC is also created.
So, is there any way to ensure that after my replica pod goes down, a new pod with the same name as the original one can be restarted?
Thanks.
When I disable failover, whether by stopping the primary pod using pg_ctl (simulating a crash) or deleting the pod, a new pod will be created (or restarted) with the same name. However, when testing the replica pod with the same operation, regardless of the method used, a new pod with a different name is restarted each time, and eventually, a new PVC is also created. So, is there any way to ensure that after my replica pod goes down, a new pod with the same name as the original one can be restarted? Thanks.