Himangini

@doctorpangloss As noted above by @cPu1 we decided that we will remove this validation and add a warning message instead to the user. Since you already have a PR open...

> > add a warning message instead to the user. > > I could but you guys don't release how poorly I know golang. @doctorpangloss alright, we'll get the fix...

Closing this since it seems like an AWS-related issue. Please feel free to reopen if these timeout errors become more frequent.

[@matthewdepietro](https://github.com/matthewdepietro) tagging you here as per your request 👍🏻

We need to come up with a plan to support this as cleanly as possible without hacks. Timebox: 1-2 days Document the outcomes here.

> > Looking into this more, a clean solution to support max pods in eksctl is to resolve the AMI using SSM, passing it as a custom AMI to the...

@pradeepnnv thanks for the feature request. ✨ @adamjohnson01 thanks for the interest in implementing this feature, we're happy to accept contributions from the community 🎉

@adamjohnson01 Wondering if you made any progress towards this, let us know if you need any assistance 👍🏻

> This issue is opened for almost 3 years @Himangini @martina-if @Callisto13 is there any ETA ? I want to avoid manual WA - https://www.arhea.net/posts/2020-06-19-amazon-eks-secondary-cidr.html @yanivpaz thanks for showing interest...

Hello @dienha93 , This doesn't seem like `eksctl` issue to me. Any issues with parsing AWS configuration files, such as incorrect handling with certain options or hard-to-understand `INIParseError` errors, will...