Store cluster meta.yaml in remote storage
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 466
- Forks
- 338
- Avg merge
- 3d 7h
- Merged PRs (30d)
- 8
Description
Feature Request
Is your feature request related to a problem? Please describe:
In the current model, we rely on the central controller to store the cluster configuration, but if the central controller is damaged, it will be very difficult to recover the cluster configuration. We have to manually write a backup task to the other machine to solve the problem.
Describe the feature you'd like:
We can add a feature to store the config folder in the remote storage when the config is updated
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by tracing where the cluster configuration is updated and how remote storage is accessed; define the recovery and update behavior, then verify that the config folder is stored remotely whenever configuration changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100