-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stop using Weave #858
Comments
How about just using the default kindnet for now? IDK if we have any deficiencies with it, but if Weave is unsupported then using the default would be our best bet until we hit something it doesn't provide. |
See submariner-io/shipyard#858. Signed-off-by: Stephen Kitt <[email protected]>
See submariner-io/shipyard#858. Signed-off-by: Stephen Kitt <[email protected]>
See submariner-io#858. Signed-off-by: Stephen Kitt <[email protected]>
See submariner-io/shipyard#858. Signed-off-by: Stephen Kitt <[email protected]>
See submariner-io/shipyard#858. Signed-off-by: Stephen Kitt <[email protected]>
See submariner-io/shipyard#858. Signed-off-by: Stephen Kitt <[email protected]>
See submariner-io/shipyard#858. Signed-off-by: Stephen Kitt <[email protected]>
Weave is no longer actively maintained, and our tests work with the default kind CNI. Until we need something more featureful, switch to the default kind CNI, and remove support for Weave altogether. See submariner-io#858. Signed-off-by: Stephen Kitt <[email protected]>
When deployed with default (aka kindnet), subctl CNI detection reports the CNI as "generic" but all the test-cases are passing fine. We can enhance the CNI detection code to detect and report the CNI in a future PR. |
See submariner-io/shipyard#858. Signed-off-by: Stephen Kitt <[email protected]>
See submariner-io/shipyard#858. Signed-off-by: Stephen Kitt <[email protected]>
See submariner-io/shipyard#858. Signed-off-by: Stephen Kitt <[email protected]>
While transitioning to kindnet CNI in our KIND deployments, it was seen that HostNetworking e2e tests were occasionally failing. On debugging this issue, it was found that kindnet CNI does not create a dedicated CNI Interface on the nodes. Submariner relies on the CNI Interface to support some of the use-cases like Health-check between the GW nodes and HostNetwork to remote cluster support. However, it was seen that as soon as we schedule a pod on the node, kindnet CNI creates a veth-xxx interface on the Host which can be used as a CNI Interface. So, in order to continue validating the above Submariner use-cases, this PR schedules a dummypod as a DaemonSet in the clusters as a workaround (and this can be removed when we switch to a different CNI). Fixes: submariner-io#966 Related to: submariner-io#858 Signed-off-by: Sridhar Gaddam <[email protected]> Signed-off-by: Tom Pantelis <[email protected]>
While transitioning to kindnet CNI in our KIND deployments, it was seen that HostNetworking e2e tests were occasionally failing. On debugging this issue, it was found that kindnet CNI does not create a dedicated CNI Interface on the nodes. Submariner relies on the CNI Interface to support some of the use-cases like Health-check between the GW nodes and HostNetwork to remote cluster support. However, it was seen that as soon as we schedule a pod on the node, kindnet CNI creates a veth-xxx interface on the Host which can be used as a CNI Interface. So, in order to continue validating the above Submariner use-cases, this PR schedules a dummypod as a DaemonSet in the clusters as a workaround (and this can be removed when we switch to a different CNI). Fixes: submariner-io#966 Related to: submariner-io#858 Signed-off-by: Sridhar Gaddam <[email protected]> Signed-off-by: Tom Pantelis <[email protected]>
While transitioning to kindnet CNI in our KIND deployments, it was seen that HostNetworking e2e tests were occasionally failing. On debugging this issue, it was found that kindnet CNI does not create a dedicated CNI Interface on the nodes. Submariner relies on the CNI Interface to support some of the use-cases like Health-check between the GW nodes and HostNetwork to remote cluster support. However, it was seen that as soon as we schedule a pod on the node, kindnet CNI creates a veth-xxx interface on the Host which can be used as a CNI Interface. So, in order to continue validating the above Submariner use-cases, this PR schedules a dummypod as a DaemonSet in the clusters as a workaround (and this can be removed when we switch to a different CNI). Fixes: #966 Related to: #858 Signed-off-by: Sridhar Gaddam <[email protected]> Signed-off-by: Tom Pantelis <[email protected]>
While transitioning to kindnet CNI in our KIND deployments, it was seen that HostNetworking e2e tests were occasionally failing. On debugging this issue, it was found that kindnet CNI does not create a dedicated CNI Interface on the nodes. Submariner relies on the CNI Interface to support some of the use-cases like Health-check between the GW nodes and HostNetwork to remote cluster support. However, it was seen that as soon as we schedule a pod on the node, kindnet CNI creates a veth-xxx interface on the Host which can be used as a CNI Interface. So, in order to continue validating the above Submariner use-cases, this PR schedules a dummypod as a DaemonSet in the clusters as a workaround (and this can be removed when we switch to a different CNI). Fixes: submariner-io#966 Related to: submariner-io#858 Signed-off-by: Sridhar Gaddam <[email protected]> Signed-off-by: Tom Pantelis <[email protected]>
While transitioning to kindnet CNI in our KIND deployments, it was seen that HostNetworking e2e tests were occasionally failing. On debugging this issue, it was found that kindnet CNI does not create a dedicated CNI Interface on the nodes. Submariner relies on the CNI Interface to support some of the use-cases like Health-check between the GW nodes and HostNetwork to remote cluster support. However, it was seen that as soon as we schedule a pod on the node, kindnet CNI creates a veth-xxx interface on the Host which can be used as a CNI Interface. So, in order to continue validating the above Submariner use-cases, this PR schedules a dummypod as a DaemonSet in the clusters as a workaround (and this can be removed when we switch to a different CNI). Fixes: submariner-io#966 Related to: submariner-io#858 Signed-off-by: Sridhar Gaddam <[email protected]> Signed-off-by: Tom Pantelis <[email protected]>
While transitioning to kindnet CNI in our KIND deployments, it was seen that HostNetworking e2e tests were occasionally failing. On debugging this issue, it was found that kindnet CNI does not create a dedicated CNI Interface on the nodes. Submariner relies on the CNI Interface to support some of the use-cases like Health-check between the GW nodes and HostNetwork to remote cluster support. However, it was seen that as soon as we schedule a pod on the node, kindnet CNI creates a veth-xxx interface on the Host which can be used as a CNI Interface. So, in order to continue validating the above Submariner use-cases, this PR schedules a dummypod as a DaemonSet in the clusters as a workaround (and this can be removed when we switch to a different CNI). Fixes: #966 Related to: #858 Signed-off-by: Sridhar Gaddam <[email protected]> Signed-off-by: Tom Pantelis <[email protected]>
See submariner-io/shipyard#858. Signed-off-by: Stephen Kitt <[email protected]>
See submariner-io/shipyard#858. Signed-off-by: Stephen Kitt <[email protected]>
See submariner-io/shipyard#858. Signed-off-by: Stephen Kitt <[email protected]>
See submariner-io/shipyard#858. Signed-off-by: Stephen Kitt <[email protected]>
See submariner-io/shipyard#858. Signed-off-by: Stephen Kitt <[email protected]>
See submariner-io/shipyard#858. Signed-off-by: Stephen Kitt <[email protected]>
See submariner-io/shipyard#858. Signed-off-by: Stephen Kitt <[email protected]>
See submariner-io/shipyard#858. Signed-off-by: Stephen Kitt <[email protected]>
See submariner-io/shipyard#858. Signed-off-by: Stephen Kitt <[email protected]>
See submariner-io/shipyard#858. Signed-off-by: Stephen Kitt <[email protected]>
See submariner-io/shipyard#858. Signed-off-by: Stephen Kitt <[email protected]>
See submariner-io/shipyard#858. Signed-off-by: Stephen Kitt <[email protected]>
See submariner-io/shipyard#858. Signed-off-by: Stephen Kitt <[email protected]>
See submariner-io/shipyard#858. Signed-off-by: Stephen Kitt <[email protected]>
See submariner-io/shipyard#858. Signed-off-by: Stephen Kitt <[email protected]>
See submariner-io/shipyard#858. Signed-off-by: Stephen Kitt <[email protected]>
See submariner-io/shipyard#858. Signed-off-by: Stephen Kitt <[email protected]> (cherry picked from commit 49c69bf)
See submariner-io/shipyard#858. Signed-off-by: Stephen Kitt <[email protected]> (cherry picked from commit 49c69bf)
See submariner-io/shipyard#858. Signed-off-by: Stephen Kitt <[email protected]> (cherry picked from commit 49c69bf)
See submariner-io/shipyard#858. Signed-off-by: Stephen Kitt <[email protected]> (cherry picked from commit 49c69bf)
See submariner-io/shipyard#858. Signed-off-by: Stephen Kitt <[email protected]>
Weave is largely unsupported upstream, and it’s not clear we actually need it specifically; we initially added Weave so that we could work on network policy support.
We should look at the current CNI space, in particular kind-friendly CNIs, and switch to whatever seems most appropriate.
The text was updated successfully, but these errors were encountered: