Skip to content
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

Closed
kiahmed opened this issue Jun 12, 2019 · 10 comments
Closed

no eksctl-managed CloudFormation stacks found #877

kiahmed opened this issue Jun 12, 2019 · 10 comments
Labels

Comments

@kiahmed
Copy link

kiahmed commented Jun 12, 2019

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

@kiahmed kiahmed added the kind/help Request for help label Jun 12, 2019
@errordeveloper
Copy link
Contributor

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.

@bcmedeiros
Copy link

Any chances of supporting this use case?

@akhon
Copy link

akhon commented Oct 24, 2019

+

@bcmedeiros
Copy link

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.

@abdennour
Copy link

@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

@peterlai-roboops
Copy link

@quickbooks2018
Copy link

quickbooks2018 commented Feb 6, 2020

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 \

   --cluster=cloudelligent-dev-eks-cluster \
   --namespace=kube-system \
   --name=alb-ingress-controller \
   --attach-policy-arn=arn:aws:iam::400812563931:policy/ALBIngressControllerIAMPolicy \
   --override-existing-serviceaccounts \
   --approve

[ℹ] eksctl version 0.13.0
[ℹ] using region us-east-1
Error: no eksctl-managed CloudFormation stacks found for "cloudelligent-dev-eks-cluster"

@quickbooks2018
Copy link

@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

https://www.youtube.com/watch?v=YqouJI3HWPI&t=226s

@sudhakarVuppalapati
Copy link

https://s3.amazonaws.com/aws-quickstart/quickstart-amazon-eks/templates/amazon-eks-master.template.yaml

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
[ℹ] eksctl version 0.13.0
[ℹ] using region eu-west-1
Error: no eksctl-managed CloudFormation stacks found for "EKS-Y8B4fXevkgeJ"

please can some help me regarding this

@serverlessguru
Copy link

serverlessguru commented Feb 22, 2020

Hitting this same issue.. Creating the EKS cluster and supporting AWS resources through CloudFormation directly.

Trying to create fargate profile:

eksctl create fargateprofile --cluster express-api-cluster --name express-api-cluster-profile --namespace kube-system --labels app=express-api --region us-east-1

Error:

Error: no eksctl-managed CloudFormation stacks found for "express-api-cluster"

What is the work around for this?

0xlen added a commit to 0xlen/amazon-eks-user-guide that referenced this issue Oct 17, 2020
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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

9 participants