Convenient local test harness for quick smoke test #58
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 4 commits
February 7, 2018 13:09
{docker,cri} × {bridge,weave}
Needs a top-level Makefile hook to control the output directory.
Signed-off-by: Ian Campbell <[email protected]>
Signed-off-by: Ian Campbell <[email protected]>
Needs a top-level Makefile hook to add a new yml to the image. Signed-off-by: Ian Campbell <[email protected]>
Add an alpine pod and use it to fetch from the nginx, which ensures that network traffic as well as DNS and such are working. Signed-off-by: Ian Campbell <[email protected]>
rn
reviewed
Feb 7, 2018
|
To be fair what you need is really |
ijc
pushed a commit
to ijc/linuxkit-kubernetes
that referenced
this pull request
Feb 12, 2018
This reverts commit 81e8953. These mounts are apparently not as redundant as they first seemed. The `runtimes.mounts` paths are all wrt the host mount namespace, so these are in fact binding the (writeable) `/var/lib/cni` paths over the (readonly) canonical host CNI paths. The `binds` will then bind those host paths into the kubelet container. Fixes linuxkit#59, I also saw this during development of linuxkit#58. Signed-off-by: Ian Campbell <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Per #19 it seems unlikely we will be getting any infrastructure to do automated boot testing soon. In the meantime add a quick rtf based test suite which does a smoke test of the supported runtime/network configurations so I can at least do a quick manual check when needed.
This boots each of the four currently supported configurations, initialises the cluster and deploys a simple web app (nginx) which is then checked for network connectivity from the host (via port forward) and for infra-pod traffic (via an alpine pod) since that is something which has been broken in the past.
Case in point, last results before posting are:
(error seems to be due to CNI paths being readonly, which is also a known fragile area, #57 touched this recently and might be the culprit, I'll investigate separately)