bpfman / bpfman/bpfman-operator
After upgarde from 4.14 to 4.16 all existing bpfprogram CRs represent instances of nodes that no longer exist in the cluster.
Open
- Dominant language
- Go
- Stars
- 38
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
The bpfman-daemon pod is stuck in the Init:ContainerCreating state, and the krprogram is in the deleting phase with the associated node missing from the cluster.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the upgrade from 4.14 to 4.16 and inspect how existing bpfprogram CRs reference nodes. Follow the bpfman-daemon pod while it remains in Init:ContainerCreating and the krprogram while it is deleting with its node missing. Done means the upgrade handles these existing resources without leaving the daemon blocked or the resource stuck deleting.
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