planetscale / planetscale/vitess-operator
Operator misbehaving when a imagePullSecrets is defined on the default service account of the namespace
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 372
- Forks
- 102
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 15
Description
When adding an imagePullSecrets in the default service account on the namespace the operator is installed on, the operator will bring all the pods up and then it will continuously recreate the vttablet pods...
It seems like the addition of imagePullSecrets by k8s is making the operator think that the pod spec has changed...
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
Start by reproducing the issue with imagePullSecrets on the namespace's default service account and observe the operator's vttablet reconciliation. Inspect where the operator compares or updates pod specifications; the fix is complete when Kubernetes-added imagePullSecrets no longer cause the vttablet pods to be continuously recreated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100