cloudnative-pg / cloudnative-pg/plugin-barman-cloud
Recovery cluster using same ClusterName
- Dominant language
- Go
- Stars
- 191
- Forks
- 72
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 18
Description
Hello dear,
Could you please help me understand why, for recovery, a different cluster name must be defined?
I was able to perform the action, but after that, changing the name also changes the k8s service name changes and all the application needs to be aligned again.
Is there a way to recover a cluster from backup, keeping the same cluster name?
Contributor guide
Research direction
No file, test, or code entry point is identified in the issue. Start by tracing the recovery workflow and how ClusterName affects the Kubernetes service name; done should establish whether the original name can be retained without breaking recovery, or document the limitation and required workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes, postgresql
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100