Skip to content

Commit 21225e1

Browse files
ousleypousleyp
authored
Merge pull request #91331 from ousleyp/cnv-52378
CNV#53278: supported limits kbase info
2 parents 341e61a + 692c30b commit 21225e1

File tree

3 files changed

+89
-0
lines changed

3 files changed

+89
-0
lines changed

‎_topic_maps/_topic_map.yml

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4522,6 +4522,8 @@ Topics:
45224522
- Name: About OKD Virtualization
45234523
File: about-virt
45244524
Distros: openshift-origin
4525+
- Name: Supported limits
4526+
File: virt-supported-limits
45254527
- Name: Security policies
45264528
File: virt-security-policies
45274529
- Name: Architecture

‎modules/virt-tested-maximums.adoc

Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,66 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * virt/about_virt/virt-supported-limits.adoc
4+
5+
:_mod-docs-content-type: REFERENCE
6+
[id="virt-tested-maximums_{context}"]
7+
= Tested maximums for {VirtProductName}
8+
9+
The following limits apply to a large-scale {VirtProductName} 4.x environment. They are based on a single cluster of the largest possible size. When you plan an environment, remember that multiple smaller clusters might be the best option for your use case.
10+
11+
[id="vm-maximums_{context}"]
12+
== Virtual machine maximums
13+
14+
The following maximums apply to virtual machines (VMs) running on {VirtProductName}. These values are subject to the limits specified in link:https://access.redhat.com/articles/rhel-kvm-limits[Virtualization limits for Red Hat{nbsp}Enterprise Linux with KVM].
15+
16+
[cols="1,1,1",subs="attributes+"]
17+
|===
18+
|Objective (per VM) |Tested limit |Theoretical limit
19+
20+
|Virtual CPUs |216 vCPUs |255 vCPUs
21+
|Memory |6 TB |16 TB
22+
|Single disk size |20 TB |100 TB
23+
|Hot-pluggable disks |255 disks |N/A
24+
|===
25+
26+
[NOTE]
27+
====
28+
Each VM must have at least 512 MB of memory.
29+
====
30+
31+
[id="host-maximums_{context}"]
32+
== Host maximums
33+
34+
The following maximums apply to the {product-title} hosts used for {VirtProductName}.
35+
36+
[cols="1,1,1",subs="attributes+"]
37+
|===
38+
|Objective (per host) |Tested limit |Theoretical limit
39+
40+
|Logical CPU cores or threads |Same as {op-system-base-full} |N/A
41+
|RAM |Same as {op-system-base} |N/A
42+
|Simultaneous live migrations |Defaults to 2 outbound migrations per node, and 5 concurrent migrations per cluster |Depends on NIC bandwidth
43+
|Live migration bandwidth |No default limit |Depends on NIC bandwidth
44+
|===
45+
46+
[id="cluster-maximums_{context}"]
47+
== Cluster maximums
48+
49+
The following maximums apply to objects defined in {VirtProductName}.
50+
51+
[cols="1,1,1",subs="attributes+"]
52+
|===
53+
|Objective (per cluster) |Tested limit |Theoretical limit
54+
55+
|Number of attached PVs per node |N/A |CSI storage provider dependent
56+
|Maximum PV size |N/A |CSI storage provider dependent
57+
|Hosts |500 hosts (100 or fewer recommended) ^[1]^ |Same as {product-title}
58+
|Defined VMs |10,000 VMs ^[2]^ |Same as {product-title}
59+
|===
60+
. If you use more than 100 nodes, consider using {rh-rhacm-first} to manage multiple clusters instead of scaling out a single control plane. Larger clusters add complexity, require longer updates, and depending on node size and total object density, they can increase control plane stress.
61+
+
62+
Using multiple clusters can be beneficial in areas like per-cluster isolation and high availability.
63+
. The maximum number of VMs per node depends on the host hardware and resource capacity. It is also limited by the following parameters:
64+
65+
* Settings that limit the number of pods that can be scheduled to a node. For example: `maxPods`.
66+
* The default number of KVM devices. For example: `devices.kubevirt.io/kvm: 1k`.

‎virt/about_virt/virt-supported-limits.adoc

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
:_mod-docs-content-type: ASSEMBLY
2+
[id="virt-supported-limits"]
3+
= Supported limits
4+
include::_attributes/common-attributes.adoc[]
5+
:context: virt-supported-limits
6+
7+
toc::[]
8+
9+
You can refer to tested object maximums when planning your {product-title} environment for {VirtProductName}. However, approaching the maximum values can reduce performance and increase latency. Ensure that you plan for your specific use case and consider all factors that can impact cluster scaling.
10+
11+
For more information about cluster configuration and options that impact performance, see the link:https://access.redhat.com/articles/6994974[{VirtProductName} - Tuning & Scaling Guide] in the Red{nbsp}Hat Knowledgebase.
12+
13+
include::modules/virt-tested-maximums.adoc[leveloffset=+1]
14+
15+
[role="_additional-resources"]
16+
[id="additional-resources_{context}"]
17+
== Additional resources
18+
* link:https://access.redhat.com/articles/6994974[{VirtProductName} - Tuning & Scaling Guide]
19+
* xref:../../scalability_and_performance/planning-your-environment-according-to-object-maximums.adoc#planning-your-environment-according-to-object-maximums[Planning your environment according to object maximums]
20+
* xref:../../nodes/nodes/nodes-nodes-managing-max-pods.adoc#nodes-nodes-managing-max-pods[Managing the maximum number of pods per node]
21+
* link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes[{rh-rhacm-title} documentation]

0 commit comments

Comments
 (0)