Open saku3071 opened 2 weeks ago
We are on latest calico 3.28 version and still facing same issue.
I'm not aware of any issues with RHEL or the environment you describe.
The error you're seeing is Calico being unable to communicate with the kube-apiserver (I think via a Service IP) - potentially an issue with the node's underlying network access to the API server, or with kube-proxy service rules.
Calico kube controller pod failling on rhel 9 , but working on rhel 7
version 3.26.1
we moving from cis aws ami rhel 7 to cis aws ami rhel 9 with same eks bootstrap code , however calico kube controllers pods were failing on rhel 9 only
ens-addon and core dns addon were failing too due to this .
pod on eks logs:
rhel 9 iptables version 1.8 legacy
Does calico works on rhel9 ? any specfiic iptables rules or issues ? or it works on specific iptables version only like 1.46 in rhel 7 ?