Skip to content

Commit 97c5a4a

Browse files
committed
Update README on dependency management
1 parent a6660cf commit 97c5a4a

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

README.md

+9
Original file line numberDiff line numberDiff line change
@@ -161,6 +161,15 @@ For example, to test [KernelMonitor](https://github.com/kubernetes/node-problem-
161161
- For [KernelMonitor](https://github.com/kubernetes/node-problem-detector/blob/master/config/kernel-monitor.json) message injection, all messages should have ```kernel: ``` prefix (also note there is a space after ```:```); or use [generator.sh](https://github.com/kubernetes/node-problem-detector/blob/master/test/kernel_log_generator/generator.sh).
162162
- To inject other logs into journald like systemd logs, use ```echo 'Some systemd message' | systemd-cat -t systemd```.
163163

164+
## Dependency Management
165+
166+
node-problem-detector uses [go modules](https://github.com/golang/go/wiki/Modules)
167+
to manage dependencies. Therefore, building node-problem-detector requires
168+
golang 1.11+. It still uses vendoring. See the
169+
[Kubernetes go modules KEP](https://github.com/kubernetes/enhancements/blob/master/keps/sig-architecture/2019-03-19-go-modules.md#alternatives-to-vendoring-using-go-modules)
170+
for the design decisions. To add a new dependency, update [go.mod](go.mod) and
171+
run `GO111MODULE=on go mod vendor`.
172+
164173
# Remedy Systems
165174

166175
A _remedy system_ is a process or processes designed to attempt to remedy problems

0 commit comments

Comments
 (0)