CRD EgressTunnel
The EgressTunnel CRD is used to record tunnel network interface information for cross-node communication. It is a cluster scope resource that corresponds one-to-one with the Kubernetes Node resource name.
apiVersion: egressgateway.spidernet.io/v1beta1
kind: EgressTunnel
metadata:
name: "node1"
status:
tunnel:
ipv4: "192.200.222.157" # (1)
ipv6: "fd01::f2" # (2)
mac: "66:50:85:cb:b2:bf" # (3)
parent:
name: "ens160" # (4)
ipv4: "10.6.1.21/16" # (5)
ipv6: "fd00::21/112" # (6)
phase: "Ready" # (7)
mark: "0x26000000" # (8)
- Tunnel IPv4 address
- Tunnel IPv6 address
- Tunnel MAC address
- Tunnel parent network interface
- Tunnel parent network interface IPv4 address
- Tunnel parent network interface IPv6 address
- Current tunnel status
Pending
: wait for IP allocationInit
: successful tunnel IP allocationReady
: the tunnel IP is allocated and tunnel is establishedFailed
: tunnel IP allocation failsHeartbeatTimeout
heartbeat Timeout for AgentNodeNotReady
Node Status is NotReady
- Packet mark value, one for each node. For example, if node A has egress traffic that needs to be forwarded to gateway node B, the traffic of node A will be marked with a mark.Each node is assigned a unique packet mark value. For instance, if Node A needs to forward Egress traffic to the gateway node B, it applies a specific mark to the packets originating from Node A.