mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
94 lines
5.4 KiB
Plaintext
94 lines
5.4 KiB
Plaintext
:_mod-docs-content-type: ASSEMBLY
|
|
:context: nodes-cluster-overcommit
|
|
[id="nodes-cluster-overcommit"]
|
|
= Configuring your cluster to place pods on overcommitted nodes
|
|
include::_attributes/common-attributes.adoc[]
|
|
|
|
toc::[]
|
|
|
|
ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
|
|
[role="_abstract"]
|
|
{product-title} administrators can control the level of overcommit and manage container density on developer containers by using the ClusterResourceOverride Operator.
|
|
|
|
[NOTE]
|
|
====
|
|
In {product-title}, you must enable cluster-level overcommit. Node overcommitment is enabled by default.
|
|
====
|
|
endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
|
|
|
|
//ROSA and Dedicated intro
|
|
ifdef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
|
|
[role="_abstract"]
|
|
{product-title} administrators can manage container density on nodes by configuring pod placement behavior and per-project resource limits that overcommit cannot exceed.
|
|
|
|
Alternatively, administrators can disable project-level resource overcommitment on customer-created namespaces that are not managed by Red Hat.
|
|
|
|
For more information about container resource management, see Additional resources.
|
|
endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
|
|
|
|
In an _overcommitted_ state, the sum of the container compute resource requestsand limits exceeds the resources available on the system. For example, you might want to use overcommitment in development environments where a trade-off of guaranteed performance for capacity is acceptable.
|
|
|
|
Containers can specify compute resource requests and limits. Requests are used for scheduling your container and provide a minimum service guarantee. Limits constrain the amount of compute resource that can be consumed on your node.
|
|
|
|
The scheduler attempts to optimize the compute resource use across all nodes in your cluster. It places pods onto specific nodes, taking the pods' compute resource requests and nodes' available capacity into consideration.
|
|
|
|
//core openshift content
|
|
ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
|
|
|
|
include::modules/nodes-cluster-overcommit-resource-requests.adoc[leveloffset=+1]
|
|
|
|
include::modules/nodes-cluster-resource-override.adoc[leveloffset=+1]
|
|
|
|
include::modules/nodes-cluster-resource-override-deploy-console.adoc[leveloffset=+2]
|
|
|
|
include::modules/nodes-cluster-resource-override-deploy-cli.adoc[leveloffset=+2]
|
|
|
|
include::modules/nodes-cluster-resource-configure.adoc[leveloffset=+2]
|
|
|
|
ifndef::openshift-rosa,openshift-dedicated[]
|
|
include::modules/nodes-cluster-resource-override-move-infra.adoc[leveloffset=+2]
|
|
endif::openshift-rosa,openshift-dedicated[]
|
|
|
|
include::modules/nodes-cluster-node-overcommit.adoc[leveloffset=+1]
|
|
|
|
include::modules/nodes-cluster-overcommit-resources-containers.adoc[leveloffset=+2]
|
|
|
|
include::modules/nodes-cluster-overcommit-qos-about.adoc[leveloffset=+2]
|
|
|
|
include::modules/nodes-qos-about-swap.adoc[leveloffset=+2]
|
|
|
|
include::modules/nodes-cluster-overcommit-configure-nodes.adoc[leveloffset=+2]
|
|
|
|
include::modules/nodes-cluster-overcommit-node-enforcing.adoc[leveloffset=+2]
|
|
|
|
include::modules/nodes-cluster-overcommit-node-resources.adoc[leveloffset=+2]
|
|
|
|
include::modules/nodes-cluster-overcommit-node-disable.adoc[leveloffset=+2]
|
|
|
|
endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
|
|
|
|
//ROSA and Dedicated can only do the following, so no ifndef on these
|
|
include::modules/nodes-cluster-project-overcommit.adoc[leveloffset=+1]
|
|
|
|
include::modules/nodes-cluster-overcommit-project-disable.adoc[leveloffset=+2]
|
|
|
|
[role="_additional-resources"]
|
|
[id="nodes-cluster-overcommit-addtl-resources"]
|
|
== Additional resources
|
|
ifndef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
|
|
* xref:../../machine_management/creating-infrastructure-machinesets.adoc#nodes-cluster-resource-override-move-infra_creating-infrastructure-machinesets[Moving the Cluster Resource Override Operator pods]
|
|
* xref:../../machine_management/creating-infrastructure-machinesets.adoc#creating-infrastructure-machinesets[Creating infrastructure machine sets]
|
|
* xref:../../applications/deployments/managing-deployment-processes.adoc#deployments-triggers_deployment-operations[Setting deployment resources]
|
|
* xref:../../nodes/clusters/nodes-cluster-overcommit.adoc#nodes-cluster-overcommit-node-enforcing_nodes-cluster-overcommit[Disabling or enforcing CPU limits using CPU CFS quotas]
|
|
* xref:../../nodes/clusters/nodes-cluster-overcommit.adoc#nodes-cluster-overcommit-node-resources_nodes-cluster-overcommit[Reserving resources for system processes]
|
|
* xref:../../nodes/clusters/nodes-cluster-overcommit.adoc#qos-about-reserve_nodes-cluster-overcommit[Understanding how to reserve memory across quality of service tiers]
|
|
* xref:../../nodes/nodes/nodes-nodes-resources-configuring.adoc#nodes-nodes-resources-configuring-setting_nodes-nodes-resources-configuring[Allocating resources for nodes]
|
|
endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
|
|
ifdef::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
|
|
* xref:../../nodes/clusters/nodes-cluster-limit-ranges.adoc#nodes-cluster-limit-ranges[Restrict resource consumption with limit ranges]
|
|
endif::openshift-rosa,openshift-rosa-hcp,openshift-dedicated[]
|
|
// TODO: Add this xref to ROSA HCP when the Support book is added.
|
|
ifndef::openshift-rosa-hcp,openshift-enterprise,openshift-dedicated[]
|
|
* xref:../../rosa_architecture/rosa_policy_service_definition/rosa-policy-responsibility-matrix.adoc#sd-managed-resources-overview_sd-managed-resources[Red Hat Managed resources]
|
|
endif::openshift-rosa-hcp,openshift-enterprise,openshift-dedicated[]
|