generated from kubernetes/kubernetes-template-project
-
Notifications
You must be signed in to change notification settings - Fork 34
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Signed-off-by: Surya Seetharaman <[email protected]>
- Loading branch information
Showing
1 changed file
with
40 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,40 @@ | ||
# NPEP-182: Add new CIDR object peer for northbound traffic | ||
|
||
* Issue: [#182](https://github.com/kubernetes-sigs/network-policy-api/issues/182) | ||
* Status: Provisional | ||
|
||
## TLDR | ||
|
||
This NPEP proposes adding support for a new CIDR object peer type for | ||
cluster egress (northbound) traffic control that can be referred in the | ||
`AdminNetworkPolicy` and `BaselineAdminNetworkPolicy` API objects using selectors. | ||
NPEP-126 already adds support for inline CIDR peer type directly on the | ||
`AdminNetworkPolicy` and `BaselineAdminNetworkPolicy` API objects. This NPEP proposes | ||
adding more extensibility by add a new CIDR object in addition to that so that | ||
users can choose either of these methods based on their needs. | ||
|
||
## Goals | ||
|
||
|
||
|
||
## Non-Goals | ||
|
||
|
||
## Introduction | ||
|
||
### User Stories for egress traffic control towards external destinations | ||
|
||
|
||
|
||
## API | ||
|
||
(... details, can point to PR with changes) | ||
|
||
|
||
## Alternatives | ||
|
||
(List other design alternatives and why we did not go in that | ||
direction) | ||
|
||
## References | ||
|