Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -21,8 +21,7 @@ The RT kernel is only supported on worker nodes.
To fully utilize the real-time mode, the containers must run with elevated privileges.
See link:https://kubernetes.io/docs/tasks/configure-pod-container/security-context/#set-capabilities-for-a-container[Set capabilities for a Container] for information on granting privileges.

{product-title} restricts the allowed capabilities, so you might need to create a `SecurityContext` as well, as explained in
link:https://docs.openshift.com/container-platform/4.1/authentication/managing-security-context-constraints.html#security-context-constraints-creating_configuring-internal-oauth[Creating Security Context Constraints].
{product-title} restricts the allowed capabilities, so you might need to create a `SecurityContext` as well.

[NOTE]
====
Expand Down
2 changes: 1 addition & 1 deletion modules/machine-config-overview.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@ The kinds of components that MCO can change include:
* **extensions**: Extend {op-system} features by adding selected pre-packaged software. For this feature, available extensions include link:https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html-single/security_hardening/index#protecting-systems-against-intrusive-usb-devices_security-hardening[usbguard] and kernel modules.
* **Custom resources (for `ContainerRuntime` and `Kubelet`)**: Outside of machine configs, MCO manages two special custom resources for modifying CRI-O container runtime settings (`ContainerRuntime` CR) and the Kubelet service (`Kubelet` CR).

The MCO is not the only Operator that can change operating system components on {product-title} nodes. Other Operators can modify operating system-level features as well. One example is the link:https://docs.openshift.com/container-platform/4.5/operators/operator-reference.html#about-node-tuning-operator_red-hat-operators[Node Tuning Operator], which allows you to do node-level tuning through Tuned daemon profiles.
The MCO is not the only Operator that can change operating system components on {product-title} nodes. Other Operators can modify operating system-level features as well. One example is the Node Tuning Operator, which allows you to do node-level tuning through Tuned daemon profiles.

Tasks for the MCO configuration that can be done post-installation are included in the following procedures. See descriptions of {op-system} bare metal installation for system configuration tasks that must be done during or before {product-title} installation.

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ You cannot assign an SCC to pods created in one of the default namespaces: `defa

.Prerequisites

* Ensure that you have the appropriate link:https://docs.openshift.com/container-platform/latest/authentication/using-rbac.html#default-roles_using-rbac[roles and permissions] to create projects, applications, and other workloads in {product-title}.
* Ensure that you have the appropriate roles and permissions to create projects, applications, and other workloads in {product-title}.

.Procedure
You can create a project using the *Developer* perspective, as follows:
Expand Down