Flannel interface disappears when restarting wireguard
On my test cluster, I am using Kubernetes with Flannel as the overlay network. I'm also using Wireguard for a vpn and p2p connections between each kubernetes node.
All node-to-node and container-to-container traffic works fine, and I can confirm the traffic goes over the wg0
(wireguard) interface. Traffic basically flows from a container to docker0
to cni0
(I think) to flannel.1
to wg0
to outside the server.
My problem is that whenever I restart wireguard with systemctl restart wg-quick@wg0
, the wg0
interface is quickly removed and re-added which causes the flannel.1
interface to disappear entirely.
I can get the flannel.1 interface back by running kubectl --namespace=kube-system delete pod -l app=flannel
, but this isn't always quick and cross-host network connectivity is disrupted until the new pods are running.
I deployed flannel on kubernetes by applying https://github.com/coreos/flannel/blob/v0.10.0/Documentation/kube-flannel.yml but with --iface=wg0
added to the flanneld args.
Is there a way to get flannel to recognize it's interface is missing and bring it back up, or some other workaround to achieve similar results?
kubernetes flannel
add a comment |
On my test cluster, I am using Kubernetes with Flannel as the overlay network. I'm also using Wireguard for a vpn and p2p connections between each kubernetes node.
All node-to-node and container-to-container traffic works fine, and I can confirm the traffic goes over the wg0
(wireguard) interface. Traffic basically flows from a container to docker0
to cni0
(I think) to flannel.1
to wg0
to outside the server.
My problem is that whenever I restart wireguard with systemctl restart wg-quick@wg0
, the wg0
interface is quickly removed and re-added which causes the flannel.1
interface to disappear entirely.
I can get the flannel.1 interface back by running kubectl --namespace=kube-system delete pod -l app=flannel
, but this isn't always quick and cross-host network connectivity is disrupted until the new pods are running.
I deployed flannel on kubernetes by applying https://github.com/coreos/flannel/blob/v0.10.0/Documentation/kube-flannel.yml but with --iface=wg0
added to the flanneld args.
Is there a way to get flannel to recognize it's interface is missing and bring it back up, or some other workaround to achieve similar results?
kubernetes flannel
add a comment |
On my test cluster, I am using Kubernetes with Flannel as the overlay network. I'm also using Wireguard for a vpn and p2p connections between each kubernetes node.
All node-to-node and container-to-container traffic works fine, and I can confirm the traffic goes over the wg0
(wireguard) interface. Traffic basically flows from a container to docker0
to cni0
(I think) to flannel.1
to wg0
to outside the server.
My problem is that whenever I restart wireguard with systemctl restart wg-quick@wg0
, the wg0
interface is quickly removed and re-added which causes the flannel.1
interface to disappear entirely.
I can get the flannel.1 interface back by running kubectl --namespace=kube-system delete pod -l app=flannel
, but this isn't always quick and cross-host network connectivity is disrupted until the new pods are running.
I deployed flannel on kubernetes by applying https://github.com/coreos/flannel/blob/v0.10.0/Documentation/kube-flannel.yml but with --iface=wg0
added to the flanneld args.
Is there a way to get flannel to recognize it's interface is missing and bring it back up, or some other workaround to achieve similar results?
kubernetes flannel
On my test cluster, I am using Kubernetes with Flannel as the overlay network. I'm also using Wireguard for a vpn and p2p connections between each kubernetes node.
All node-to-node and container-to-container traffic works fine, and I can confirm the traffic goes over the wg0
(wireguard) interface. Traffic basically flows from a container to docker0
to cni0
(I think) to flannel.1
to wg0
to outside the server.
My problem is that whenever I restart wireguard with systemctl restart wg-quick@wg0
, the wg0
interface is quickly removed and re-added which causes the flannel.1
interface to disappear entirely.
I can get the flannel.1 interface back by running kubectl --namespace=kube-system delete pod -l app=flannel
, but this isn't always quick and cross-host network connectivity is disrupted until the new pods are running.
I deployed flannel on kubernetes by applying https://github.com/coreos/flannel/blob/v0.10.0/Documentation/kube-flannel.yml but with --iface=wg0
added to the flanneld args.
Is there a way to get flannel to recognize it's interface is missing and bring it back up, or some other workaround to achieve similar results?
kubernetes flannel
kubernetes flannel
asked Nov 21 '18 at 21:45
user2514458user2514458
84
84
add a comment |
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53420909%2fflannel-interface-disappears-when-restarting-wireguard%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53420909%2fflannel-interface-disappears-when-restarting-wireguard%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown