Azure Container/Kubernetes Service - Network interface and IPs are not deleted
1
Azure Container/Kubernetes Service - Virtual Network :
IPs and network interface are not deleted/cleaned after pods deletion.
No more available address in the subnet that kubernetes use after a few deployments.
Is there a way to clean those network interface?
azure kubernetes azure-container-service azure-kubernetes asked Nov 13 '18 at 20:44
BenBen
351110
add a comment |
1
Azure Container/Kubernetes Service - Virtual Network :
IPs and network interface are not deleted/cleaned after pods deletion.
No more available address in the subnet that kubernetes use after a few deployments.
Is there a way to clean those network interface?
azure kubernetes azure-container-service azure-kubernetes asked Nov 13 '18 at 20:44
BenBen
351110
1
what's the Kubernetes version? This used to be a problem in acs-engine/azure-cni but it should be long fixed in AKS (reference)
– alev
Nov 13 '18 at 21:35
Shouldn't you delete the deployment of the pods? Maybe I do not really understand it.
– Charles Xu
Nov 14 '18 at 14:09
@alev: the kubernetes version is 1.11.13
– Ben
Nov 14 '18 at 17:52
@CharlesXu-MSFT This problem occurs when I delete a namespace or a specific deployment, AKS does not remove the network interfaces related to the namespace or the deployments/pods.
– Ben
Nov 14 '18 at 17:53
add a comment |
1
1
1
1
Azure Container/Kubernetes Service - Virtual Network :
IPs and network interface are not deleted/cleaned after pods deletion.
No more available address in the subnet that kubernetes use after a few deployments.
Is there a way to clean those network interface?
azure kubernetes azure-container-service azure-kubernetes asked Nov 13 '18 at 20:44
BenBen
351110
Azure Container/Kubernetes Service - Virtual Network :
IPs and network interface are not deleted/cleaned after pods deletion.
No more available address in the subnet that kubernetes use after a few deployments.
Is there a way to clean those network interface?
azure kubernetes azure-container-service azure-kubernetes azure kubernetes azure-container-service azure-kubernetes asked Nov 13 '18 at 20:44
BenBen
351110
asked Nov 13 '18 at 20:44
BenBen
351110
asked Nov 13 '18 at 20:44
BenBen
351110
asked Nov 13 '18 at 20:44
BenBen
351110
asked Nov 13 '18 at 20:44
BenBen
351110
351110
1
what's the Kubernetes version? This used to be a problem in acs-engine/azure-cni but it should be long fixed in AKS (reference)
– alev
Nov 13 '18 at 21:35
Shouldn't you delete the deployment of the pods? Maybe I do not really understand it.
– Charles Xu
Nov 14 '18 at 14:09
@alev: the kubernetes version is 1.11.13
– Ben
Nov 14 '18 at 17:52
@CharlesXu-MSFT This problem occurs when I delete a namespace or a specific deployment, AKS does not remove the network interfaces related to the namespace or the deployments/pods.
– Ben
Nov 14 '18 at 17:53
add a comment |
1
what's the Kubernetes version? This used to be a problem in acs-engine/azure-cni but it should be long fixed in AKS (reference)
– alev
Nov 13 '18 at 21:35
Shouldn't you delete the deployment of the pods? Maybe I do not really understand it.
– Charles Xu
Nov 14 '18 at 14:09
@alev: the kubernetes version is 1.11.13
– Ben
Nov 14 '18 at 17:52
@CharlesXu-MSFT This problem occurs when I delete a namespace or a specific deployment, AKS does not remove the network interfaces related to the namespace or the deployments/pods.
– Ben
Nov 14 '18 at 17:53
1
1
what's the Kubernetes version? This used to be a problem in acs-engine/azure-cni but it should be long fixed in AKS (reference)
– alev
Nov 13 '18 at 21:35
what's the Kubernetes version? This used to be a problem in acs-engine/azure-cni but it should be long fixed in AKS (reference)
– alev
Nov 13 '18 at 21:35
Shouldn't you delete the deployment of the pods? Maybe I do not really understand it.
– Charles Xu
Nov 14 '18 at 14:09
Shouldn't you delete the deployment of the pods? Maybe I do not really understand it.
– Charles Xu
Nov 14 '18 at 14:09
@alev: the kubernetes version is 1.11.13
– Ben
Nov 14 '18 at 17:52
@alev: the kubernetes version is 1.11.13
– Ben
Nov 14 '18 at 17:52
@CharlesXu-MSFT This problem occurs when I delete a namespace or a specific deployment, AKS does not remove the network interfaces related to the namespace or the deployments/pods.
– Ben
Nov 14 '18 at 17:53
@CharlesXu-MSFT This problem occurs when I delete a namespace or a specific deployment, AKS does not remove the network interfaces related to the namespace or the deployments/pods.
– Ben
Nov 14 '18 at 17:53
add a comment |
2 Answers
2
active
oldest
votes
2
RESOLVED:
By default, AKS is reserving 31 ips for each node in the cluster so my problem was not that the IPs were not released but just that a lot of IPs were reserved :)
answered Nov 15 '18 at 21:22
BenBen
351110
Well spotted. +1
– VonC
Nov 15 '18 at 21:41
add a comment |
0
You can try and see if you can:
Remove IP addresses,
Delete a network interface and/or- find and delete unattached network interface cards (NICs) for Azure VMs
answered Nov 13 '18 at 21:06
VonCVonC
838k29426523193
thats not really a solution, right?
– 4c74356b41
Nov 13 '18 at 21:16
@VonC I used the script from script to find and delete unattached network interface but the problem is that those network interfaces are still connected to the VMs that belongs to the AKS cluster. AKS should be the one freeing the network interfaces after a deletion happen in the cluster...
– Ben
Nov 13 '18 at 21:22
@Ben Strange. May be this is an ownership issue? (as in github.com/Azure/AKS/issues/427#issuecomment-397368508)
– VonC
Nov 13 '18 at 21:36
add a comment |
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
});
}
});
draft saved
draft discarded
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%2f53289211%2fazure-container-kubernetes-service-network-interface-and-ips-are-not-deleted%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
2
RESOLVED:
By default, AKS is reserving 31 ips for each node in the cluster so my problem was not that the IPs were not released but just that a lot of IPs were reserved :)
answered Nov 15 '18 at 21:22
BenBen
351110
Well spotted. +1
– VonC
Nov 15 '18 at 21:41
add a comment |
2
RESOLVED:
By default, AKS is reserving 31 ips for each node in the cluster so my problem was not that the IPs were not released but just that a lot of IPs were reserved :)
answered Nov 15 '18 at 21:22
BenBen
351110
Well spotted. +1
– VonC
Nov 15 '18 at 21:41
add a comment |
2
2
2
RESOLVED:
By default, AKS is reserving 31 ips for each node in the cluster so my problem was not that the IPs were not released but just that a lot of IPs were reserved :)
answered Nov 15 '18 at 21:22
BenBen
351110
RESOLVED:
By default, AKS is reserving 31 ips for each node in the cluster so my problem was not that the IPs were not released but just that a lot of IPs were reserved :)
answered Nov 15 '18 at 21:22
BenBen
351110
answered Nov 15 '18 at 21:22
BenBen
351110
answered Nov 15 '18 at 21:22
BenBen
351110
answered Nov 15 '18 at 21:22
BenBen
351110
351110
Well spotted. +1
– VonC
Nov 15 '18 at 21:41
add a comment |
Well spotted. +1
– VonC
Nov 15 '18 at 21:41
Well spotted. +1
– VonC
Nov 15 '18 at 21:41
Well spotted. +1
– VonC
Nov 15 '18 at 21:41
add a comment |
0
You can try and see if you can:
Remove IP addresses,
Delete a network interface and/or- find and delete unattached network interface cards (NICs) for Azure VMs
answered Nov 13 '18 at 21:06
VonCVonC
838k29426523193
thats not really a solution, right?
– 4c74356b41
Nov 13 '18 at 21:16
@VonC I used the script from script to find and delete unattached network interface but the problem is that those network interfaces are still connected to the VMs that belongs to the AKS cluster. AKS should be the one freeing the network interfaces after a deletion happen in the cluster...
– Ben
Nov 13 '18 at 21:22
@Ben Strange. May be this is an ownership issue? (as in github.com/Azure/AKS/issues/427#issuecomment-397368508)
– VonC
Nov 13 '18 at 21:36
add a comment |
0
You can try and see if you can:
Remove IP addresses,
Delete a network interface and/or- find and delete unattached network interface cards (NICs) for Azure VMs
answered Nov 13 '18 at 21:06
VonCVonC
838k29426523193
thats not really a solution, right?
– 4c74356b41
Nov 13 '18 at 21:16
@VonC I used the script from script to find and delete unattached network interface but the problem is that those network interfaces are still connected to the VMs that belongs to the AKS cluster. AKS should be the one freeing the network interfaces after a deletion happen in the cluster...
– Ben
Nov 13 '18 at 21:22
@Ben Strange. May be this is an ownership issue? (as in github.com/Azure/AKS/issues/427#issuecomment-397368508)
– VonC
Nov 13 '18 at 21:36
add a comment |
0
0
0
You can try and see if you can:
Remove IP addresses,
Delete a network interface and/or- find and delete unattached network interface cards (NICs) for Azure VMs
answered Nov 13 '18 at 21:06
VonCVonC
838k29426523193
You can try and see if you can:
Remove IP addresses,
Delete a network interface and/or- find and delete unattached network interface cards (NICs) for Azure VMs
answered Nov 13 '18 at 21:06
VonCVonC
838k29426523193
answered Nov 13 '18 at 21:06
VonCVonC
838k29426523193
answered Nov 13 '18 at 21:06
VonCVonC
838k29426523193
answered Nov 13 '18 at 21:06
VonCVonC
838k29426523193
838k29426523193
thats not really a solution, right?
– 4c74356b41
Nov 13 '18 at 21:16
@VonC I used the script from script to find and delete unattached network interface but the problem is that those network interfaces are still connected to the VMs that belongs to the AKS cluster. AKS should be the one freeing the network interfaces after a deletion happen in the cluster...
– Ben
Nov 13 '18 at 21:22
@Ben Strange. May be this is an ownership issue? (as in github.com/Azure/AKS/issues/427#issuecomment-397368508)
– VonC
Nov 13 '18 at 21:36
add a comment |
thats not really a solution, right?
– 4c74356b41
Nov 13 '18 at 21:16
@VonC I used the script from script to find and delete unattached network interface but the problem is that those network interfaces are still connected to the VMs that belongs to the AKS cluster. AKS should be the one freeing the network interfaces after a deletion happen in the cluster...
– Ben
Nov 13 '18 at 21:22
@Ben Strange. May be this is an ownership issue? (as in github.com/Azure/AKS/issues/427#issuecomment-397368508)
– VonC
Nov 13 '18 at 21:36
thats not really a solution, right?
– 4c74356b41
Nov 13 '18 at 21:16
thats not really a solution, right?
– 4c74356b41
Nov 13 '18 at 21:16
@VonC I used the script from script to find and delete unattached network interface but the problem is that those network interfaces are still connected to the VMs that belongs to the AKS cluster. AKS should be the one freeing the network interfaces after a deletion happen in the cluster...
– Ben
Nov 13 '18 at 21:22
@VonC I used the script from script to find and delete unattached network interface but the problem is that those network interfaces are still connected to the VMs that belongs to the AKS cluster. AKS should be the one freeing the network interfaces after a deletion happen in the cluster...
– Ben
Nov 13 '18 at 21:22
@Ben Strange. May be this is an ownership issue? (as in github.com/Azure/AKS/issues/427#issuecomment-397368508)
– VonC
Nov 13 '18 at 21:36
@Ben Strange. May be this is an ownership issue? (as in github.com/Azure/AKS/issues/427#issuecomment-397368508)
– VonC
Nov 13 '18 at 21:36
add a comment |
draft saved
draft discarded
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.
draft saved
draft discarded
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%2f53289211%2fazure-container-kubernetes-service-network-interface-and-ips-are-not-deleted%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
1
what's the Kubernetes version? This used to be a problem in acs-engine/azure-cni but it should be long fixed in AKS (reference)
– alev
Nov 13 '18 at 21:35
Shouldn't you delete the deployment of the pods? Maybe I do not really understand it.
– Charles Xu
Nov 14 '18 at 14:09
@alev: the kubernetes version is 1.11.13
– Ben
Nov 14 '18 at 17:52
@CharlesXu-MSFT This problem occurs when I delete a namespace or a specific deployment, AKS does not remove the network interfaces related to the namespace or the deployments/pods.
– Ben
Nov 14 '18 at 17:53