planetscale / planetscale/vitess-operator
Bug Report: Not able to list backups using kubectl get vitessbackups
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 372
- Forks
- 102
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 15
Description
Moving https://github.com/vitessio/vitess/issues/14766 here as it is related to the vitess-operator.
cc @GenLN as the original author.
Overview of the Issue
This is not working for 2 vitess cluster (only for one in separate namespace) on same K8S cluster.
Reproduction Steps
- Deploy operator and CRD into namespace A
- Deploy vitess cluster1 on namespace A
- Run full backups
- Run kubectl get vitessbackups into namespace A(it works)
- Update operator deployment and assign also to watch namespace B
- Deploy vitess cluster2 on namespace B
- Run full backups
- Run kubectl get vitessbackups into namespace B (empty for cluster2, even the backups are done and uploaded to gcs,s3 etc...)
- Run kubectl get vitessbackups into namespace A(list for cluster1 vitessbackups are shown)
Second test different K8S cluster:
- Deploy operator and CRD into namespace A1
- Deploy cluster11 into namespace A1
- Run full backups
- Run kubectl get vitessbackups into namespace A1 for cluster11(backup list shown)
- Deploy Operator deployment kind only into namespace B1
- Deploy cluster21 into namespace B1
- Run full backups
- Run kubectl get vitessbackups into namespace B1 for cluster 21 (empty list no backups shown)
- Run kubectl get vitessbackups into namespace A1 for cluster 11 (vitessbackups list shown)
Binary Version
Vitess v18.0.1
latest tag vitess operator
Operating System and Environment details
K8S cluster
Log Fragments
No response
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
Reproduce the namespace A/B setup with the operator watching both namespaces, then inspect how VitessBackup resources are discovered and listed. Compare the operator-only deployment and the shared deployment cases, and verify the fix by confirming kubectl get vitessbackups shows completed backups in both namespaces.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100