planetscale / planetscale/vitess-operator
backup pod unable to start with failed to fetch service account token
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 372
- Forks
- 102
- Avg merge
- 3d 5h
- Merged PRs (30d)
- 15
Description
Consistently got this error event when trying to startup a vitess cluster on GKE Autopilot running k8s v1.22.10 and vitess 14.0.1, tried both operator version 2.7.1 and 2.7.2 both failed. The cluster config I am using is similar to the exampledb as provided.
MountVolume.SetUp failed for volume "kube-api-access-x6hpj" : failed to fetch token: serviceaccounts "vitess-operator" is forbidden: the UID in the bound object reference (4d8d96fd-b40a-484d-90ad-a55e46df2f01) does not match the UID in record. The object might have been deleted and then recreated
I have found that the error messages comes from https://github.com/kubernetes/kubernetes/blob/master/plugin/pkg/admission/noderestriction/admission.go#L537 so I am not sure if this is a operator problem or a k8s problem.
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 with the reported Kubernetes event and the Kubernetes admission.go reference, then compare the exampledb-like cluster configuration across Vitess 14.0.1 and operator 2.7.1/2.7.2 on GKE Autopilot. Determine whether the token failure originates in the operator or Kubernetes; the issue is done when the cause and a verified fix or workaround are identified.
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
- Needs clarification
- Newbie friendliness
- 25/100