OpenShift Security Context Constraints: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 7: | Line 7: | ||
=Internal= | =Internal= | ||
* [[OpenShift_Security_Concepts#Security_Context_Constraints|OpenShift Security Concepts | * [[OpenShift_Security_Concepts#Security_Context_Constraints|OpenShift Security Concepts]] | ||
=Overview= | =Overview= | ||
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. | ||
Revision as of 20:45, 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#install-config-persistent-storage-pod-security-context
- https://docs.openshift.com/container-platform/3.7/admin_guide/manage_scc.html
Internal
Overview
OpenShift uses Security Context Constraints (SCCs) to control the actions that a pod can perform and what it has the ability to access.