containers / containers/nri-plugins
Using plugins out of tree / not with Kubernetes?
- Dominant language
- Go
- Stars
- 114
- Forks
- 44
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 20
Description
Hi! I'm particularly interested in these two for functionality:
- https://github.com/containers/nri-plugins/blob/main/pkg/sysfs/system.go
- https://github.com/containers/nri-plugins/blob/main/cmd/plugins/balloons/policy/cputree.go#L243
And I'm wondering if 1) you have examples of using these outside of the context of Kubernetes, and 2) if it might be possible to vendor them separately to allow for such use cases? For some background, I'm designing extractors for compatibility, and nri was recommended to me as an alternative for topology to hwloc, which has technically "[go bindings](https://github.com/c0mm4nd/go-hwloc/pull/2)" but I'm finding them hard to use. If you'd be interested in this idea I can prototype / test the out of tree case, although it would be helpful to understand how to create the various plugins. Thanks!
Contributor guide
Research direction
Start by reading pkg/sysfs/system.go and the balloons policy code at cmd/plugins/balloons/policy/cputree.go:243, then trace how the referenced functionality depends on the surrounding plugins. Determine whether these components can be used outside Kubernetes and vendored separately; done means the standalone-use path, plugin creation guidance, or a concrete prototype and test is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100