Commits on Mar 1, 2022

1. Realize Egress for a Pod once its network is created …

   Previously antrea-controller included a Pod in an EgressGroup only when
   its IP has been presented in K8s API. If a Pod tries to access external
   right after it's up, Node IP will be used as the SNAT IP even when an
   Egress applying to it has been created because its Pod IP may haven't
   been reported to K8s API or antrea-controller may haven't included the
   Pod in the EgressGroup.
   
   This patch fixes it by making CNIServer notify EgressController that it
   has processed CNI ADD request of a Pod, then EgressController can
   reconcile the corresponding Egress immediately, instead of waiting for
   the Pod to be reported to K8s API. As NetworkPolicyController relies on
   that event as well, we introduce a channel implementation which supports
   multiple subscribers.
   
   Fixes antrea-io#3361
   
   Signed-off-by: Quan Tian <qtian@vmware.com>

   

   tnqn committed Mar 1, 2022
   Configuration menu

   • View commit details
   • Copy full SHA for c24e914
   • Browse repository at this point

   Copy the full SHA

   c24e914 View commit details

   Browse the repository at this point in the history