-pod-container/configure- liveness-readiness-probes/]. In order for kubelet to run these health checks for each pod, by default, Cilium will always allow all ingress traffic from the local host to each ingress master-sg (self) health checks 4240/tcp ingress worker-sg health checks ICMP 8/0 ingress master-sg (self) health checks ICMP 8/0 ingress worker-sg health checks 8472/udp egress master-sg (self) VXLAN overlay 4240/tcp egress master-sg (self) health checks 4240/tcp egress worker-sg health checks ICMP 8/0 egress master-sg (self) health checks Port Range / Protocol Ingress/Egress Source/Des�na�on

re-pod-container/configure-liveness-readiness-probes/]. In order for kubelet to run these health checks for each pod, by default, Cilium will always allow all ingress traffic from the local host to each master-sg (self) health checks 4240/tcp ingress worker-sg health checks Port Range / Protocol Ingress/Egress Source/Destination Description ICMP 8/0 ingress master-sg (self) health checks ICMP 8/0 ingress worker-sg health checks 8472/udp egress master-sg (self) VXLAN overlay 8472/udp egress worker-sg VXLAN overlay 4240/tcp egress master-sg (self) health checks 4240/tcp egress worker-sg health checks ICMP 8/0

where Cilium partially replaces and optimizes kube-proxy functionality. As opposed to probe which checks the underlying kernel for available BPF features and automatically disables components responsible configured. To disable the feature, set config.sessionAffinity=false. LoadBalancer Source Ranges Checks When a LoadBalancer service is configured with spec.loadBalancerSourceRanges, Cilium’s eBPF kube-proxy are limited, run the Operator with option --aws-release-excess- ips=true. When enabled, operator checks the number of IPs regularly and attempts to release excess free IPs from ENI. It is generally a good

where Cilium partially replaces and optimizes kube-proxy functionality. As opposed to probe which checks the underlying kernel for available eBPF features and automatically disables components responsible The health check server is accessible via the HTTP /healthz endpoint. LoadBalancer Source Ranges Checks When a LoadBalancer service is configured with spec.loadBalancerSourceRanges, Cilium’s eBPF kube-proxy are limited, run the Operator with option --aws-release-excess- ips=true. When enabled, operator checks the number of IPs regularly and attempts to release excess free IPs from ENI. It is generally a good

where Cilium partially replaces and optimizes kube-proxy functionality. As opposed to probe which checks the underlying kernel for available eBPF features and automatically disables components responsible The health check server is accessible via the HTTP /healthz endpoint. LoadBalancer Source Ranges Checks When a LoadBalancer service is configured with spec.loadBalancerSourceRanges, Cilium’s eBPF kube-proxy are limited, run the Operator with option --aws-release-excess- ips=true. When enabled, operator checks the number of IPs regularly and attempts to release excess free IPs from ENI. It is generally a good

where Cilium partially replaces and optimizes kube-proxy functionality. As opposed to probe which checks the underlying kernel for available eBPF features and automatically disables components responsible The health check server is accessible via the HTTP /healthz endpoint. LoadBalancer Source Ranges Checks When a LoadBalancer service is configured with spec.loadBalancerSourceRanges, Cilium’s eBPF kube-proxy are limited, run the Operator with option --aws-release-excess- ips=true. When enabled, operator checks the number of IPs regularly and attempts to release excess free IPs from ENI. It is generally a good

where Cilium partially replaces and optimizes kube-proxy functionality. As opposed to probe which checks the underlying kernel for available BPF features and automatically disables components responsible are limited, run the Operator with option --aws-release-excess- ips=true. When enabled, operator checks the number of IPs regularly and attempts to release excess free IPs from ENI. It is generally a good re-pod-container/configure-liveness-readiness-probes/]. In order for kubelet to run these health checks for each pod, by default, Cilium will always allow all ingress traffic from the local host to each

analysis to ensure that eBPF programs are safe for the kernel, or sometimes the hardware, to run. It checks that the process loading the eBPF program holds the required capabilities (privileges), the program