Skip to content

Issues: containernetworking/cni

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.

Sign up for GitHub

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

Clear current search query, filters, and sorts
7 Open 24 Closed
7 Open 24 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Clarify if the error payload's cniVersion should be the version passed in via the input payload (network config object) or the spec version the plugin supports component/spec
#827 opened Mar 31, 2021 by passcod
3
Clarification needed: behaviour of VERSION command in version mismatch scenario component/spec
#826 opened Mar 31, 2021 by passcod
Please clarify network name in spec component/spec
#552 opened May 9, 2018 by bboreham v1.0.0
3
Spec: clarify how DEL should be called in cases of failure component/spec help wanted
#530 opened Jan 25, 2018 by squeed
1
Instead of type shouldn't we have a network field ? component/spec kind/design
#128 opened Feb 18, 2016 by asridharan
9
spec: add ability for ADD to return arbitrary k/v data to be passed back to DEL component/spec kind/design kind/enhancement
#75 opened Oct 30, 2015 by eyakubovich
4
CNI should have something to say about limiting cross-talk component/spec kind/design kind/enhancement
#47 opened Aug 27, 2015 by eyakubovich
1
ProTip! Mix and match filters to narrow down what you’re looking for.