Skip to content

Commit

Permalink
docs: add a user story for network ns goals to KNI KEP
Browse files Browse the repository at this point in the history
Signed-off-by: Shane Utt <[email protected]>
  • Loading branch information
shaneutt committed Feb 1, 2024
1 parent 8a33b31 commit 0c3fb89
Showing 1 changed file with 7 additions and 0 deletions.
7 changes: 7 additions & 0 deletions keps/sig-network/4410-k8s-network-interface/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -77,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

0 comments on commit 0c3fb89

Please sign in to comment.