Each VIP is configured with a set of PODs.
More...
Each VIP is configured with a set of PODs.
Definition at line 92 of file kp.h.
ip46_address_t kp_pod_t::address |
Destination address used to transfer traffic towards to that POD.
The address is also used pod ID and pseudo-random seed for the load-balancing process.
Definition at line 103 of file kp.h.
The next DPO in the graph to follow.
Definition at line 144 of file kp.h.
Registration to FIB event.
Definition at line 96 of file kp.h.
Some per-POD flags.
For now only KP_POD_FLAGS_USED is defined.
Definition at line 116 of file kp.h.
Rotating timestamp of when KP_POD_FLAGS_USED flag was last set.
POD removal is based on garbage collection and reference counting. When an POD is removed, there is a race between configuration core and worker cores which may still add a reference while it should not be used. This timestamp is used to not remove the POD while a race condition may happen.
Definition at line 129 of file kp.h.
u32 kp_pod_t::next_hop_child_index |
The child index on the FIB entry.
Definition at line 139 of file kp.h.
The FIB entry index for the next-hop.
Definition at line 134 of file kp.h.
PODs are indexed by address and VIP Index.
Which means there will be duplicated if the same server address is used for multiple VIPs.
Definition at line 110 of file kp.h.
The documentation for this struct was generated from the following file:
- src/plugins/kubeproxy/kp.h