OpenShift Security Context Constraints: Difference between revisions
Jump to navigation
Jump to search
| Line 14: | Line 14: | ||
OpenShift uses Security Context Constraints (SCCs) to control the actions that a pod can perform and what it has the ability to access. | OpenShift uses Security Context Constraints (SCCs) to control the actions that a pod can perform and what it has the ability to access. | ||
<font color=red> | |||
* What is it? | |||
* What are its components? | |||
* What can it do? | |||
* How is one associated with a container? | |||
</font> | |||
Revision as of 21:29, 22 January 2018
External
- https://docs.openshift.com/container-platform/latest/architecture/additional_concepts/authorization.html#security-context-constraints
- https://docs.openshift.com/container-platform/latest/install_config/persistent_storage/pod_security_context.html
- https://docs.openshift.com/container-platform/latest/admin_guide/manage_scc.html
Internal
- OpenShift Security Concepts
- Docker Concepts - Privileged Container
- Security Context Constrains Operations
Overview
OpenShift uses Security Context Constraints (SCCs) to control the actions that a pod can perform and what it has the ability to access.
- What is it?
- What are its components?
- What can it do?
- How is one associated with a container?