Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Recovery cluster using same ClusterName

Open
#727 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
go, kubernetes, postgresql
Domain
databases, infrastructure

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.

Description

question

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?

Dominant language
Go
Stars
192
Forks
75
Avg merge
1d 7h
Merged PRs (30d)
17

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cloudnative-pg/plugin-barman-cloud

All issues in cloudnative-pg/plugin-barman-cloud

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.