Skip to content
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

Closed
skitt opened this issue Jul 6, 2022 · 2 comments · Fixed by #956
Closed

Stop using Weave #858

skitt opened this issue Jul 6, 2022 · 2 comments · Fixed by #956
Assignees
Labels
dependencies Pull requests that update a dependency file maintenance Small tasks related to ongoing maintenance release-note-needed

Comments

@skitt
Copy link
Member

skitt commented Jul 6, 2022

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.

@mkolesnik
Copy link
Collaborator

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.

skitt added a commit to skitt/lighthouse that referenced this issue Sep 20, 2022
skitt added a commit to skitt/submariner that referenced this issue Sep 20, 2022
skitt added a commit to skitt/shipyard that referenced this issue Sep 20, 2022
skitt added a commit to skitt/releases that referenced this issue Sep 20, 2022
skitt added a commit to skitt/submariner-charts that referenced this issue Sep 20, 2022
skitt added a commit to skitt/submariner-operator that referenced this issue Sep 20, 2022
skitt added a commit to skitt/subctl that referenced this issue Sep 20, 2022
@skitt skitt self-assigned this Sep 20, 2022
@skitt skitt added dependencies Pull requests that update a dependency file maintenance Small tasks related to ongoing maintenance and removed next-version-candidate labels Sep 20, 2022
skitt added a commit to skitt/shipyard that referenced this issue Sep 20, 2022
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]>
@sridhargaddam
Copy link
Member

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.

tpantelis pushed a commit to submariner-io/releases that referenced this issue Sep 20, 2022
tpantelis pushed a commit to submariner-io/submariner-charts that referenced this issue Sep 20, 2022
tpantelis pushed a commit to submariner-io/lighthouse that referenced this issue Sep 20, 2022
tpantelis added a commit to tpantelis/shipyard that referenced this issue Oct 12, 2022
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]>
tpantelis added a commit to tpantelis/shipyard that referenced this issue Oct 12, 2022
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]>
tpantelis added a commit that referenced this issue Oct 12, 2022
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]>
tpantelis added a commit to tpantelis/shipyard that referenced this issue Oct 12, 2022
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]>
tpantelis added a commit to tpantelis/shipyard that referenced this issue Oct 12, 2022
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]>
tpantelis added a commit that referenced this issue Oct 12, 2022
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]>
tpantelis pushed a commit to tpantelis/lighthouse that referenced this issue Oct 12, 2022
tpantelis pushed a commit to submariner-io/submariner that referenced this issue Oct 12, 2022
tpantelis pushed a commit to submariner-io/submariner that referenced this issue Oct 12, 2022
tpantelis pushed a commit to tpantelis/lighthouse that referenced this issue Oct 12, 2022
tpantelis pushed a commit to tpantelis/submariner-operator that referenced this issue Oct 12, 2022
tpantelis pushed a commit to tpantelis/submariner-operator that referenced this issue Oct 12, 2022
tpantelis pushed a commit to submariner-io/submariner-operator that referenced this issue Oct 12, 2022
tpantelis pushed a commit to submariner-io/lighthouse that referenced this issue Oct 12, 2022
tpantelis pushed a commit to submariner-io/lighthouse that referenced this issue Oct 12, 2022
tpantelis pushed a commit to submariner-io/submariner-operator that referenced this issue Oct 12, 2022
tpantelis pushed a commit to tpantelis/subctl that referenced this issue Oct 12, 2022
tpantelis pushed a commit to tpantelis/submariner-charts that referenced this issue Oct 12, 2022
tpantelis pushed a commit to tpantelis/submariner-charts that referenced this issue Oct 12, 2022
tpantelis pushed a commit to submariner-io/subctl that referenced this issue Oct 12, 2022
tpantelis pushed a commit to submariner-io/submariner-charts that referenced this issue Oct 12, 2022
tpantelis pushed a commit to submariner-io/submariner-charts that referenced this issue Oct 12, 2022
sridhargaddam pushed a commit to sridhargaddam/releases that referenced this issue Nov 23, 2022
See submariner-io/shipyard#858.

Signed-off-by: Stephen Kitt <[email protected]>
(cherry picked from commit 49c69bf)
skitt added a commit to submariner-io/releases that referenced this issue Nov 23, 2022
See submariner-io/shipyard#858.

Signed-off-by: Stephen Kitt <[email protected]>
(cherry picked from commit 49c69bf)
mkolesnik pushed a commit to mkolesnik/releases that referenced this issue Dec 12, 2022
See submariner-io/shipyard#858.

Signed-off-by: Stephen Kitt <[email protected]>
(cherry picked from commit 49c69bf)
mkolesnik pushed a commit to submariner-io/releases that referenced this issue Dec 12, 2022
See submariner-io/shipyard#858.

Signed-off-by: Stephen Kitt <[email protected]>
(cherry picked from commit 49c69bf)
novad03 pushed a commit to novad03/k8s-submariner that referenced this issue Nov 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file maintenance Small tasks related to ongoing maintenance release-note-needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants