Skip to content

Commit

Permalink
Merge pull request #130 from tssurya/remove-user-story-folder
Browse files Browse the repository at this point in the history
Remove user story folder
  • Loading branch information
k8s-ci-robot authored Aug 9, 2023
2 parents bf98cec + 4d834c3 commit 2b8d2e4
Show file tree
Hide file tree
Showing 4 changed files with 26 additions and 97 deletions.
94 changes: 0 additions & 94 deletions docs/userstories/README.md

This file was deleted.

1 change: 0 additions & 1 deletion docs/userstories/v1/README.md

This file was deleted.

1 change: 0 additions & 1 deletion docs/userstories/v2/README.md

This file was deleted.

27 changes: 26 additions & 1 deletion npep/npep-95.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,14 +13,39 @@

## Non-Goals

(What is out of scope for this proposal.)
(What is explicitly out of scope for this proposal.)

## Introduction

(Can link to external doc -- but we should bias towards copying
the content into the NPEP as online documents are easier to lose
-- e.g. owner messes up the permissions, accidental deletion)

## User-Stories/Use-Cases

(What new user-stories/use-cases does this proposal introduce?)

A user story should typically have a summary structured this way:

1. **As a** [user concerned by the story]
2. **I want** [goal of the story]
3. **so that** [reason for the story]

The “so that” part is optional if more details are provided in the description.
A story can also be supplemented with examples, diagrams, or additional notes.

e.g

Story 1: Deny traffic at a cluster level

As a cluster admin, I want to apply non-overridable deny rules to certain pod(s)
and(or) Namespace(s) that isolate the selected resources from all other cluster
internal traffic.

For Example: The admin wishes to protect a sensitive namespace by applying an
AdminNetworkPolicy which denies ingress from all other in-cluster resources
for all ports and protocols.

## API

(... details, can point to PR with changes)
Expand Down

0 comments on commit 2b8d2e4

Please sign in to comment.