mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-05-06 05:03:27 +00:00
* 1228 Overlay test for Windows nodes * Apply suggestions from code review Co-authored-by: Sunil Singh <sunil.singh@suse.com> * updated note about error message * versioned note on 2.0-2.4 --------- Co-authored-by: Sunil Singh <sunil.singh@suse.com>
This commit is contained in:
committed by
GitHub
parent
2980926dd8
commit
54dc6b187b
+1
-1
@@ -19,7 +19,7 @@ The pod can be scheduled to any of the hosts you used for your cluster, but that
|
||||
|
||||
To test the overlay network, you can launch the following `DaemonSet` definition. This will run a `swiss-army-knife` container on every host (image was developed by Rancher engineers and can be found here: https://github.com/rancherlabs/swiss-army-knife), which we will use to run a `ping` test between containers on all hosts.
|
||||
|
||||
> **Note:** This container [does not support ARM nodes](https://github.com/leodotcloud/swiss-army-knife/issues/18), such as a Raspberry Pi. This will be seen in the pod logs as `exec user process caused: exec format error`.
|
||||
> **Note:** The `swiss-army-knife` container does not support Windows nodes. It also [does not support ARM nodes](https://github.com/leodotcloud/swiss-army-knife/issues/18), such as a Raspberry Pi. When the test encounters incompatible nodes, this is recorded in the pod logs as an error message, such as `exec user process caused: exec format error` for ARM nodes, or `ImagePullBackOff (Back-off pulling image "rancherlabs/swiss-army-knife)` for Windows nodes.
|
||||
|
||||
1. Save the following file as `overlaytest.yml`
|
||||
|
||||
|
||||
Reference in New Issue
Block a user