IP Support and Restriction for data network and SR-IOV interface. (r8, dsr8)
Updated the IP support table with data network and SR-IOV interface in pod. Change-Id: I946434e45d9331bf5f08fdb5912203a45012b26e Signed-off-by: Dinesh Neelapu <dinesh.neelapu@windriver.com>
This commit is contained in:
parent
72ffc9c3a3
commit
c682174768
@ -8,7 +8,7 @@ IP Support
|
|||||||
|
|
||||||
|prod| supports IPv4 and IPv6 versions for various networks.
|
|prod| supports IPv4 and IPv6 versions for various networks.
|
||||||
|
|
||||||
All networks must be a single address family, either IPv4 or IPv6, with the
|
All platform networks must be a single address family, either IPv4 or IPv6, with the
|
||||||
exception of the |PXE| boot network which must always use IPv4. The following
|
exception of the |PXE| boot network which must always use IPv4. The following
|
||||||
table lists IPv4 and IPv6 support for different networks:
|
table lists IPv4 and IPv6 support for different networks:
|
||||||
|
|
||||||
@ -40,3 +40,18 @@ table lists IPv4 and IPv6 support for different networks:
|
|||||||
- Y
|
- Y
|
||||||
- Y
|
- Y
|
||||||
- The Cluster Host network supports IPv4 or IPv6 addressing.
|
- The Cluster Host network supports IPv4 or IPv6 addressing.
|
||||||
|
* - Data Network and |SRIOV| Interface
|
||||||
|
- Y
|
||||||
|
- Y
|
||||||
|
- There is no restriction for the Data Network and |SRIOV| Interfaces to
|
||||||
|
have the same address family as the platform. They operate independently
|
||||||
|
from the platform and are capable of supporting both IPv4 and IPv6
|
||||||
|
addressing, offering flexible options for network connectivity. However,
|
||||||
|
IPv4 or IPv6 requires dedicated |IPAM| pools or static address
|
||||||
|
configuration to use the corresponding address families with the |SRIOV|
|
||||||
|
Interfaces. For more information about |IPAM| pools configuration, see
|
||||||
|
https://docs.tigera.io/calico/latest/reference/resources/ippool.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user