Hello, I need your help guys. I am using the lates...
# generalm
magnificent-rainbow-12629
07/24/2025, 9:04 AMHello, I need your help guys. I am using the latest stable Rancher version and trying to deploy an EKS cluster with custom AMI. When i deploy a node group without passing a custom AMI (using default one), everything is perfect and working. Cluster is healthy and rancher marks it as healthy. When i try to create a new node group with custom AMI (small modifications of ubuntu EKS AMI to meet my needs) without passing user-data, the node group creation fails because nodes cannot register to the cluster. If i pass user-data with bootstrap.sh then the nodes are registered to the cluster and node group is created correctly but then Rancher complains that it cannot find the rancher agent and doesn't show the cluster as healthy in the UI. What is the correct way to use Custom AMI with EKS downstream cluster and have Rancher agent installed on the nodes?
magnificent-rainbow-12629
07/24/2025, 11:42 AMForget, it looks like the problem is on the ubuntu image:
I get this error for coredns on the node and this causes the rest of the issues:
Copy code
2025-07-24T11:38:00.401742103Z stdout F [ERROR] plugin/kubernetes: Unhandled Error
2025-07-24T11:38:01.281971933Z stdout F [INFO] plugin/kubernetes: pkg/mod/k8s.io/client-go@v0.31.2/tools/cache/reflector.go:243: failed to list *v1.EndpointSlice: Get "<https://10.100.0.1:443/apis/discovery.k8s.io/v1/endpointslices?limit=500&resourceVersion=0>": dial tcp 10.100.0.1:443: i/o timeout
2025-07-24T11:38:01.282001544Z stdout F [ERROR] plugin/kubernetes: Unhandled Error
2025-07-24T11:38:02.179321198Z stdout F [INFO] plugin/ready: Still waiting on: "kubernetes"
2025-07-24T11:38:12.179498318Z stdout F [INFO] plugin/ready: Still waiting on: "kubernetes"
2025-07-24T11:38:22.179968228Z stdout F [INFO] plugin/ready: Still waiting on: "kubernetes"
2025-07-24T11:38:32.179315813Z stdout F [INFO] plugin/ready: Still waiting on: "kubernetes"
2025-07-24T11:38:33.886289367Z stdout F [INFO] plugin/kubernetes: pkg/mod/k8s.io/client-go@v0.31.2/tools/cache/reflector.go:243: failed to list *v1.Service: Get "<https://10.100.0.1:443/api/v1/services?limit=500&resourceVersion=0>": dial tcp 10.100.0.1:443: i/o timeout
2025-07-24T11:38:33.886319803Z stdout F [ERROR] plugin/kubernetes: Unhandled Error
2025-07-24T11:38:35.68710731Z stdout F [INFO] plugin/kubernetes: pkg/mod/k8s.io/client-go@v0.31.2/tools/cache/reflector.go:243: failed to list *v1.EndpointSlice: Get "<https://10.100.0.1:443/apis/discovery.k8s.io/v1/endpointslices?limit=500&resourceVersion=0>": dial tcp 10.100.0.1:443: i/o timeout
2025-07-24T11:38:35.687136071Z stdout F [ERROR] plugin/kubernetes: Unhandled Error
2025-07-24T11:38:35.966224337Z stdout F [INFO] plugin/kubernetes: pkg/mod/k8s.io/client-go@v0.31.2/tools/cache/reflector.go:243: failed to list *v1.Namespace: Get "<https://10.100.0.1:443/api/v1/namespaces?limit=500&resourceVersion=0>": dial tcp 10.100.0.1:443: i/o timeout2 Views