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.

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

docs: kni add goal for container network namespaces #6

Merged
merged 2 commits into from
Feb 1, 2024
Merged

docs: kni add goal for container network namespaces #6

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8a33b31
docs: add goal about Pod network ns APIs
shaneutt Feb 1, 2024
0c3fb89
docs: add a user story for network ns goals to KNI KEP
shaneutt Feb 1, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 10 additions & 2 deletions keps/sig-network/4410-k8s-network-interface/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,8 +50,9 @@ and accommodate advanced functionalities and potential areas for expansion.
9. Provide the ability to identify the IP address family without parsing the value (such as a field)
10. Provide as much backwards-compatibility with CNI as is feasible
11. Guarantee the network is setup and in a healthy state before containers are started (ephemeral, init, regular)
12. Provide support for Kata and other virtualized runtimes
13. Provide a reference implementation
12. If feasible, provide API awareness of Pod network namespaces (e.g. interface names)
13. Provide support for Kata and other virtualized runtimes
14. Provide a reference implementation

### Non-Goals

Expand All @@ -76,6 +77,13 @@ As a cluster operator, I need the ability to determine what networks are availab

As a Kubernetes developer, I need the ability to have extension points for pod network setup, teardown and update so that I can support future Kubernetes networking features with either reducing the changes to core kubernetes or eliminating them

#### Story 4

As a tool which manages eBPF programs on a Kubernetes cluster (bpfman,
inspektorgadget), I would like to be able to see the network interfaces of a
`Pod` via the Kubernetes API so that I can attach TC/XDP network programs to
those interfaces based on knowing the Pod name.

### Notes/Constraints/Caveats

Changes to the pod specification will require hard evidence.
Expand Down