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
390f2692
Commit
390f2692
authored
May 06, 2015
by
Maxwell Forbes
Browse files
Options
Browse Files
Download
Plain Diff
Merge pull request #7836 from pmorie/security-context-doc
Fix link to service accounts doc in security context doc
parents
302de065
a6b06f49
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
1 deletion
+1
-1
security_context.md
docs/design/security_context.md
+1
-1
No files found.
docs/design/security_context.md
View file @
390f2692
...
@@ -32,7 +32,7 @@ Processes in pods will need to have consistent UID/GID/SELinux category labels i
...
@@ -32,7 +32,7 @@ Processes in pods will need to have consistent UID/GID/SELinux category labels i
*
The concept of a security context should not be tied to a particular security mechanism or platform
*
The concept of a security context should not be tied to a particular security mechanism or platform
(ie. SELinux, AppArmor)
(ie. SELinux, AppArmor)
*
Applying a different security context to a scope (namespace or pod) requires a solution such as the one proposed for
*
Applying a different security context to a scope (namespace or pod) requires a solution such as the one proposed for
[
service accounts
](
https://github.com/GoogleCloudPlatform/kubernetes/pull/2297
)
.
[
service accounts
](
./service_accounts.md
)
.
## Use Cases
## Use Cases
...
...
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