containerd / containerd/go-cni
Establish cadence for regularly updating CNI
Open
- Dominant language
- Go
- Stars
- 162
- Forks
- 69
- PR merge metrics
- No merged PRs in 30d
Description
Need to decide when to update CNI and establish a cadence process.
- [ ] coordinate updating cni and plugins across the stack
#56
- [ ] evaluate new cni cache config apis
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by reviewing issue #56 and the existing CNI and plugin update process, then evaluate the referenced CNI cache configuration APIs. Done means the update cadence, coordinated stack process, and cache API evaluation are documented and agreed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100