mirror of
https://github.com/k3s-io/kubernetes.git
synced 2026-07-23 02:00:12 +00:00
1057407cee
Instead of hard-coding two instances of the hostpathplugin which listen on
certain socket paths, the hostpathplugin now gets started through Pod exec as
needed. The advantage is that the helper code is in charge of socket naming,
just like it would be in real deployment.
One nuisance is that exec.StreamWithContext always complains in copyFromStdout
and copyFromStderr when the remote hostpathplugin gets killed via context
cancellation:
E0312 11:56:31.637669 289446 v2.go:167] "Unhandled Error" err="next reader: read tcp [::1]:59006->[::1]:6444: use of closed network connection" logger="UnhandledError"
E0312 11:56:31.637749 289446 v2.go:150] "Unhandled Error" err="next reader: read tcp [::1]:59006->[::1]:6444: use of closed network connection" logger="UnhandledError"
These can be ignored.
test/e2e/testing-manifests
Embedded Test Data
In case one needs to use any test fixture inside your tests and those are defined inside this directory, they need to be added to the //go:embed directive in embed.go.
For example, if one wants to include this Readme as a test fixture (potential bad idea in reality!),
// embed.go
...
//go:embed some other files README.md
...
This fixture can be accessed in the e2e tests using test/e2e/framework/testfiles.Read like
testfiles.Read("test/e2e/testing-manifests/README.md).
This is needed since migrating to //go:embed from go-bindata.