You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Today on Azure CNI Overlay with Calico as network policy, there is a short delay between when the pod starts and when Calico allows outbound traffic from the pod. there is no explanation for why, but I believe that it's the same reason it is for AWS CNI with Calico, until kubelet adds the POD IP to the pod spec, calico is blocking the traffic. kubernetes/kubernetes#39113
Describe alternatives you've considered
why not implement something similar? adding sleep to pods startup or alternative patches are not a real solution. or companies that still dont want to use cilium.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Today on Azure CNI Overlay with Calico as network policy, there is a short delay between when the pod starts and when Calico allows outbound traffic from the pod. there is no explanation for why, but I believe that it's the same reason it is for AWS CNI with Calico, until kubelet adds the POD IP to the pod spec, calico is blocking the traffic.
kubernetes/kubernetes#39113
Describe the solution you'd like
AWS solves this issue using AWS CNI
https://github.com/aws/amazon-vpc-cni-k8s?tab=readme-ov-file#annotate_pod_ip-v193:~:text=ANNOTATE_POD_IP%20(v1.9.3%2B
Describe alternatives you've considered
why not implement something similar? adding sleep to pods startup or alternative patches are not a real solution. or companies that still dont want to use cilium.
The text was updated successfully, but these errors were encountered: