Replies: 1 comment
-
For anyone who encounter this issue, turns out the custom image that we're using is blocking the ip forwarding, so we need to enable it like this: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
We're currently using a custom CIS Amazon Linux 2 Kernel 5.10 Benchmark - Level 1 on our EKS cluster. We also use nodegroup with launch template to manage our worker nodes. Everything seems working except CoreDNS pods won't run properly.
Kubernetes version: 1.27.17
Pod logs:
journalctl logs:
Beta Was this translation helpful? Give feedback.
All reactions