-
Bug
-
Resolution: Done
-
Normal
-
None
-
4.16, 4.17, 4.18
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
In this section:
While the Egress IPs capability manages the IP address capacity per node, it is important to plan for this constraint in your deployments. For example, for a cluster installed on bare-metal infrastructure with 8 nodes you can configure 150 egress IP addresses. However, if a public cloud provider limits IP address capacity to 10 IP addresses per node, the total number of assignable IP addresses is only 80. To achieve the same IP address capacity in this example cloud provider, you would need to allocate 7 additional nodes.
There is discussion of limits, but there are actually no limits on bare metal, only cloud. Also, the section is titled "public cloud platform consideration" so it shouldn't mention bare metal. Perhaps there needs to be a new section to address bare metal instead of conflating the information between cloud and bare metal.