pingcap / pingcap/tidb-operator
BR: backup path should start with 'gs' when storage is gcs
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 540
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 18
Description
Bug Report
What version of Kubernetes are you using?
What version of TiDB Operator are you using?
master
What storage classes exist in the Kubernetes cluster and what are used for PD/TiKV pods?
What's the status of the TiDB cluster pods?
What did you do?
backup cr's backupPath is start with gcs when storage is gcs. but the path should start with gs. ref https://cloud.google.com/storage/docs/gsutil#syntax.
What did you expect to see?
backup cr's backupPath start with gs.
What did you see instead?
backup cr's backupPath start with gcs.
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
Search the backup CR handling for the backupPath value used when storage is gcs; the issue does not name a file or test. Check the generated Backup resource and any existing storage-path tests, if present, and consider the work done when the GCS path uses gs rather than gcs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gcp, go, kubernetes
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100