Skip to content
Projects
Groups
Snippets
Help
This project
Loading...
Sign in / Register
Toggle navigation
K
k3s
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
Jacklull
k3s
Commits
ea53fd76
Commit
ea53fd76
authored
Apr 25, 2016
by
Adam Pyle
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Incorrect attribute - docs - pod-security-context
Pod definition had incorrect spelling on attribute `securityContext` Also fixed the flow of Motivation intro paragraph.
parent
c5df0bf2
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
pod-security-context.md
docs/proposals/pod-security-context.md
+2
-2
No files found.
docs/proposals/pod-security-context.md
View file @
ea53fd76
...
...
@@ -40,7 +40,7 @@ order to correctly model pod- and container-level security concerns.
## Motivation
Currently, containers have a
`SecurityContext`
attribute which contains information about the
security settings the container uses. In practice many of these attributes are uniform across all
security settings the container uses. In practice
,
many of these attributes are uniform across all
containers in a pod. Simultaneously, there is also a need to apply the security context pattern
at the pod level to correctly model security attributes that apply only at a pod level.
...
...
@@ -277,7 +277,7 @@ to implement, explain, and support. Instead, we will approach backward compatib
securityContext:
runAsUser: 1001
- name: b
securityConte
s
t:
securityConte
x
t:
runAsUser: 1002
```
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment