aws-load-balancer-controller crashing on RHEL8 worker node.

[deepshock-211120]

Environment:

• AWS Region: ap-southeast-1
• Instance Type(s): m5.large
• EKS Platform version: "eks.3"
• Kubernetes version : "1.20"
• AMI Version: "1.20"
• Kernel (e.g. uname -a):4.18.0-348.2.1.el8_5.x86_64

Hello all,

I have followed the amazon-eks-custom-amis to create CIS-hardened (OS level) custom ami for both AL2 and RHEL8.

Was able to create node group and tested joining to both 1.20 and 1.18 clusters successfully for AL2 custom AMI.

Was able to create another node group and tested joining to both 1.20 and 1.18 clusters successfully for RHEL8 custom AMI (with the tweak to add "sudo modprobe iptables" into the bootstrap procedure.

I wish to have EKS cluster with RHEL8-only worker nodes.

However, I am facing an issue to stablize aws-load-balancer-controller deployment on RHEL8 worker nodes. The error got is

# {"level":"error","ts":":***********..7923973,"logger":"controller-runtime.manager","msg":"Failed to get API Group-Resources","error":"Get \"https://10.100.0.1:443/api?timeout=32s\": dial tcp 10.100.0.1:443: i/o timeout"}
# {"level":"error","ts":":***********..7924356,"logger":"setup","msg":"unable to start manager","error":"Get \"https://10.100.0.1:443/api?timeout=32s\": dial tcp 10.100.0.1:443: i/o timeout"}

When I pin the deployment to AL2 nodes. It works perfectly. The security group, node role IAM policy for RHEL8 nodes and AL2 nodes are exactly the same.

Appreciate your help here.

[jayanthvn]

@deepshock-211120 - This is the correct repo - https://github.com/kubernetes-sigs/aws-load-balancer-controller for AWS LB controller.

[github-actions[bot]]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see. If you need more assistance, please open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.