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

Ignore NetNS path errors on delete #686

Merged
merged 1 commit into from
Jan 19, 2022

Conversation

silenceper
Copy link
Contributor

@silenceper silenceper commented Jan 6, 2022

fix #685

Signed-off-by: silenceper <[email protected]>
@silenceper
Copy link
Contributor Author

/PTAL @dcbw

@dcbw dcbw changed the title fix #685 Ignore NetNS path errors on delete Jan 19, 2022
@squeed
Copy link
Member

squeed commented Jan 19, 2022

Great! Thanks

@matthewdupre matthewdupre merged commit de5cffe into containernetworking:master Jan 19, 2022
aanm pushed a commit to cilium/cilium that referenced this pull request Jul 28, 2022
If the network namespace has been deleted before CNI DEL is invoked,
Cilium CNI should still invoke the delegated IPAM plugin to
release the IP address.

This matches the behavior of the "bridge" reference plugin,
which invokes delegated plugin DEL when the network
namespace has been deleted:
containernetworking/plugins#685
containernetworking/plugins#686

I tested the changes in a kind cluster configuring Cilium CNI
to use the reference host-local plugin for IPAM. The cilium
connectivity tests pass. I also repeatedly deleted pods
from a deployment to trigger the "Unable to enter namespace"
warning in the Cilium CNI logs, then verified that the
delegated IPAM plugin DEL was invoked to release the IPs.

Signed-off-by: Will Daly <[email protected]>
dezmodue pushed a commit to dezmodue/cilium that referenced this pull request Aug 10, 2022
If the network namespace has been deleted before CNI DEL is invoked,
Cilium CNI should still invoke the delegated IPAM plugin to
release the IP address.

This matches the behavior of the "bridge" reference plugin,
which invokes delegated plugin DEL when the network
namespace has been deleted:
containernetworking/plugins#685
containernetworking/plugins#686

I tested the changes in a kind cluster configuring Cilium CNI
to use the reference host-local plugin for IPAM. The cilium
connectivity tests pass. I also repeatedly deleted pods
from a deployment to trigger the "Unable to enter namespace"
warning in the Cilium CNI logs, then verified that the
delegated IPAM plugin DEL was invoked to release the IPs.

Signed-off-by: Will Daly <[email protected]>
nbusseneau pushed a commit to nbusseneau/cilium that referenced this pull request Aug 10, 2022
[ upstream commit 645c8d5 ]

If the network namespace has been deleted before CNI DEL is invoked,
Cilium CNI should still invoke the delegated IPAM plugin to
release the IP address.

This matches the behavior of the "bridge" reference plugin,
which invokes delegated plugin DEL when the network
namespace has been deleted:
containernetworking/plugins#685
containernetworking/plugins#686

I tested the changes in a kind cluster configuring Cilium CNI
to use the reference host-local plugin for IPAM. The cilium
connectivity tests pass. I also repeatedly deleted pods
from a deployment to trigger the "Unable to enter namespace"
warning in the Cilium CNI logs, then verified that the
delegated IPAM plugin DEL was invoked to release the IPs.

Signed-off-by: Will Daly <[email protected]>
Signed-off-by: Nicolas Busseneau <[email protected]>
tklauser pushed a commit to cilium/cilium that referenced this pull request Aug 11, 2022
[ upstream commit 645c8d5 ]

If the network namespace has been deleted before CNI DEL is invoked,
Cilium CNI should still invoke the delegated IPAM plugin to
release the IP address.

This matches the behavior of the "bridge" reference plugin,
which invokes delegated plugin DEL when the network
namespace has been deleted:
containernetworking/plugins#685
containernetworking/plugins#686

I tested the changes in a kind cluster configuring Cilium CNI
to use the reference host-local plugin for IPAM. The cilium
connectivity tests pass. I also repeatedly deleted pods
from a deployment to trigger the "Unable to enter namespace"
warning in the Cilium CNI logs, then verified that the
delegated IPAM plugin DEL was invoked to release the IPs.

Signed-off-by: Will Daly <[email protected]>
Signed-off-by: Nicolas Busseneau <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

If the NetNS path does not exist, error should not be returned, otherwise it may cause ip leakage
3 participants