microsoft / microsoft/sql-server-samples
Error starting pods: pod has unbound immediate PersistentVolumeClaims
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 11.2k
- Forks
- 9.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 14
Description
I tried it locally with Minikube and then in a Jelastic k8s cluster with dynamic nfs volume provisioning. In both cases the above error pops up. However, 3 PVCs are marked as bound. Can you suggest how I can investigate it?
Contributor guide
No contributing guide indexed for this repository
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 pod startup error in the Minikube or Jelastic Kubernetes environments described in the issue. Inspect the pod's PVC references and compare them with the three PVCs reported as bound, including the dynamic NFS provisioning details. Done means identifying which claim remains unbound and documenting the cause or a confirmed investigation path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100