-
Bug
-
Resolution: Done
-
Major
-
4.13.z, 4.12.z, 4.14.z, 4.15.z, 4.17.z, 4.16.z
-
Quality / Stability / Reliability
-
False
-
-
5
-
None
-
None
-
None
-
None
-
Rejected
-
OSDOCS Sprint 267, OSDOCS Sprint 268, OSDOCS Sprint 269
-
3
-
Done
-
Release Note Not Required
-
N/A
-
None
-
None
-
None
-
None
Description of problem:
1. OpenShift MetalLB configuration documentation has an issue where it does not specify how to assign a single IP address in the IPAddressPool section. [1] 2. In metallb documentation [2], it is mentioned that a single IP address can be assigned using the /32 CIDR notation (e.g., 192.168.1.2/32), but this detail is missing in OpenShift metallb configuration documentation. Either this can be added as a note : ~~~ To specify a single IP address in a pool, use /32 in the CIDR notation (e.g. 192.168.1.2/32). ~~~ Or, Can be added as part of example. ~~~ apiVersion: metallb.io/v1beta1 kind: IPAddressPool metadata: name: doc-example-single-ip namespace: metallb-system spec: addresses: - 192.168.1.2/32 - 192.168.1.21/32 - 192.168.1.31/32 ~~~ In the above example shows how to configure multiple specific IP's in IPAddressPool CR, instead of providing the complete network range. [1] https://docs.openshift.com/container-platform/4.18/networking/metallb/metallb-configure-address-pools.html#example-reserve-ip-addresses [2] https://metallb.universe.tf/configuration/_advanced_ipaddresspool_configuration/
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info: