File tree Expand file tree Collapse file tree 4 files changed +26
-97
lines changed Expand file tree Collapse file tree 4 files changed +26
-97
lines changed Load Diff This file was deleted.
Load Diff This file was deleted.
Load Diff This file was deleted.
Original file line number Diff line number Diff line change 13
13
14
14
## Non-Goals
15
15
16
- (What is out of scope for this proposal.)
16
+ (What is explicitly out of scope for this proposal.)
17
17
18
18
## Introduction
19
19
20
20
(Can link to external doc -- but we should bias towards copying
21
21
the content into the NPEP as online documents are easier to lose
22
22
-- e.g. owner messes up the permissions, accidental deletion)
23
23
24
+ ## User-Stories/Use-Cases
25
+
26
+ (What new user-stories/use-cases does this proposal introduce?)
27
+
28
+ A user story should typically have a summary structured this way:
29
+
30
+ 1 . ** As a** [ user concerned by the story]
31
+ 2 . ** I want** [ goal of the story]
32
+ 3 . ** so that** [ reason for the story]
33
+
34
+ The “so that” part is optional if more details are provided in the description.
35
+ A story can also be supplemented with examples, diagrams, or additional notes.
36
+
37
+ e.g
38
+
39
+ Story 1: Deny traffic at a cluster level
40
+
41
+ As a cluster admin, I want to apply non-overridable deny rules to certain pod(s)
42
+ and(or) Namespace(s) that isolate the selected resources from all other cluster
43
+ internal traffic.
44
+
45
+ For Example: The admin wishes to protect a sensitive namespace by applying an
46
+ AdminNetworkPolicy which denies ingress from all other in-cluster resources
47
+ for all ports and protocols.
48
+
24
49
## API
25
50
26
51
(... details, can point to PR with changes)
You can’t perform that action at this time.
0 commit comments