New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
no eksctl-managed CloudFormation stacks found #877
Comments
Hi @kiahmed this is unsupported at the moment. If you need help, please send me an email - ilya@weave.works and we can discuss your use-case. |
Any chances of supporting this use case? |
|
I ended up recreating my cluster, and I understand it would be very hard to support "adopting" a manually created cluster, especially because CloudFormation also does not support adopting existing resources. |
@brunojcm I got the same error, even though, I didn't create the cluster manually. Instead I used this terraform module : terraform-aws-modules/terraform-aws-eks |
|
same issue, any updates? I am using Terraform for deployment, why eksctl bound with Cloudformation? root@ubuntu:/home/asim/Desktop/eks/environment/dev# eksctl create iamserviceaccount \
[ℹ] eksctl version 0.13.0 |
|
me too getting Error: no eksctl-managed CloudFormation stacks found for "EKS-Y8B4fXevkgeJ" eksctl create iamserviceaccount --region eu-west-1 --name alb-ingress-controller --namespace kube-system --cluster EKS-Y8B4fXevkgeJ --attach-policy-arn arn:aws:iam::CCCCCC:policy/ALBIngressControllerIAMPolicy --override-existing-serviceaccounts --approve please can some help me regarding this |
Hitting this same issue.. Creating the EKS cluster and supporting AWS resources through CloudFormation directly. Trying to create fargate profile:
Error:
What is the work around for this? |
The eksctl may report error `no eksctl-managed CloudFormation stacks found for <...>`, change it to use CloudFormation template to launch self-managed nodegroup. See: eksctl-io/eksctl#877
getting VPC configuration for cluster "my-clstr": no eksctl-managed CloudFormation stacks found for "my-clstr"
created the cluster with aws console as it wasnt working with eksctl for existing vpc and subnet mix, but when try to create a node group on the existing vpc get the error which makes sense but is there a work around for this. Dont ask me why I couldn't create clstr with eksctl in first place we already went through that and its not possible for my req
What help do you need?
Describe the type of help you need
The text was updated successfully, but these errors were encountered: