Skip to content

Commit aef81b5

Browse files
committed
Add NPEP for new CIDR object peer
Signed-off-by: Surya Seetharaman <[email protected]>
1 parent 95ae2f8 commit aef81b5

File tree

1 file changed

+40
-0
lines changed

1 file changed

+40
-0
lines changed

npeps/npep-182-cidr-object-peer.md

Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
# NPEP-182: Add new CIDR object peer for northbound traffic
2+
3+
* Issue: [#182](https://github.com/kubernetes-sigs/network-policy-api/issues/182)
4+
* Status: Provisional
5+
6+
## TLDR
7+
8+
This NPEP proposes adding support for a new CIDR object peer type for
9+
cluster egress (northbound) traffic control that can be referred in the
10+
`AdminNetworkPolicy` and `BaselineAdminNetworkPolicy` API objects using selectors.
11+
NPEP-126 already adds support for inline CIDR peer type directly on the
12+
`AdminNetworkPolicy` and `BaselineAdminNetworkPolicy` API objects. This NPEP proposes
13+
adding more extensibility by add a new CIDR object in addition to that so that
14+
users can choose either of these methods based on their needs.
15+
16+
## Goals
17+
18+
19+
20+
## Non-Goals
21+
22+
23+
## Introduction
24+
25+
### User Stories for egress traffic control towards external destinations
26+
27+
28+
29+
## API
30+
31+
(... details, can point to PR with changes)
32+
33+
34+
## Alternatives
35+
36+
(List other design alternatives and why we did not go in that
37+
direction)
38+
39+
## References
40+

0 commit comments

Comments
 (0)