eksctl
eksctl copied to clipboard
[Bug] EC2 not added to EKS
I have successfully created a cluster in AWS with this command/file:
eksctl create cluster -f mycluster.yaml
---
apiVersion: eksctl.io/v1alpha5
kind: ClusterConfig
metadata:
name: my-cluster
region: eu-central-1
version: "1.23"
nodeGroups:
- name: ng-my
instanceType: t3.xlarge
desiredCapacity: 3
minSize: 2
maxSize: 5
tags:
'Name': 'my-cluster'
cloudWatch:
clusterLogging:
enableTypes: ["audit", "authenticator", "controllerManager"]
ec2 was successfully created, but they were not added to the EKS cluster, so I get this message after the command kubectl get nodes: No resources found
Earlier with previous versions of eksctl (before 1.13) and kubernetes 1.21 there was no problem and ec2 was always added to EKS, but with version eksctl 1.15 this problem appeared.
Hello maxinfosoft :wave: Thank you for opening an issue in eksctl
project. The team will review the issue and aim to respond within 1-3 business days. Meanwhile, please read about the Contribution and Code of Conduct guidelines here. You can find out more information about eksctl
on our website
@maxinfosoft, do you have any logs you can share from the command? Can you confirm your kubectl is configured to use my-cluster
and not some other cluster?
-do you have any logs you can share from the command? The command ended without error messages.
-Can you confirm your kubectl is configured to use my-cluster and not some other cluster? Yes, I confirm that kubectl (kubectx) is configured for this cluster.
FYI, this console command did not help:: eksctl upgrade cluster -f .\my-cluster.yaml
The command ended without error messages.
Logs would still aid us in debugging the issue. Please share the logs if you have them.
Can you try deleting and recreating the nodegroup using eksctl delete nodegroup -f mycluster.yaml
followed by eksctl create nodegroup -f mycluster.yaml
, and share logs from the command?
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This issue was closed because it has been stalled for 5 days with no activity.