NRI plugin add config failPolicy, eg. skip、fail
- Dominant language
- Go
- Stars
- 406
- Forks
- 102
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 8
Description
### What is the problem you're trying to solve
When NRI plugin is shutdown, containerd Will not reject container creation,If there is important logic in the CreateContainer method, such as injecting devices into the container, some containers may be missed during the restart of the nri plugin.
### Describe the solution you'd like
Therefore, can we configure the failPolicy of each nri plugin, such as skip and fail? When the configuration is skip, the restart of the nri plugin is ignored, and when the configuration is fail, the container is refused to be created.
### Additional context
_No response_
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the NRI plugin CreateContainer path and the containerd behavior when the plugin is restarted or shut down. Determine where per-plugin configuration is read and how skip versus fail should affect container creation. Done means both policies are configurable and their restart behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100