Eksctl: How to export CloudFormation template that would be applied

[toothbrush]

I hope that i haven't missed anything looking at the documentation, but it appears that it's not easy to get eksctl to tell me the CloudFormation that was used to create a particular cluster. While i've found eksctl great for spinning up a cluster for a test-drive, i'd like to move forward to using EKS in production, but i can't do that without having some CloudFormation to check into our infrastructure deployment repository.

Currently i'm considering using eksctl to bring up a cluster, then something like stackup[cfn-stack-name] template > my-cloudformation.json to be able to check that in to version control, but that feels rather ugly. Is there a recommended approach?

I've seen #181 but i'd rather use native CloudFormation than Terraform, which we try to avoid at my org (we're pretty scared of state).

Apologies if i've overlooked something! Thanks for an ergonomic tool!

[errordeveloper]

This is actually being worked on. We have #718, which @pawelprazak started, and I picked it up last week.

[toothbrush]

Amazing! Having actually just properly inspected the resulting stacks with stackup, i now see the concerns about the UserData depending on inputs at cluster creation time (referenced here) (and probably other things i haven't yet discovered). I'm guessing the PR you reference addresses this?

It looks promising anyway — thank you for your efforts! 🙌

[errordeveloper]

Yes, we will need to get cluster credential at build time.

The latest version of the code is in feature-utils-export branch, in case you might want to take a look.

[Snarik]

This would be immensely useful to me as well.

[pcolazurdo]

Quick one, is this still being worked on? The branch feature-utils-export doesn't seem to exist

[sgrzemski-ias]

Any update?

[owenthereal]

Is this being worked on? This feature is very useful!

[koslib]

I guess I'm repeating what the last people also said, this feature is indeed very useful. Especially for environments where a lot of developers are involved and drift occurs on the CF stack, this could help bring things back to normal.

Any updates with the timeline of this feature?

[koslib]

I'll pick this issue up for development and hopefully will have something soon-ish. If anyone else is already taking a look and want to collab on it, feel free to reach out.

[ghasemel]

I also need that, I've exported the templates using aws command but for this, you need to run the eksctl to create the stacks first.
aws cloudformation get-template --stack-name myteststack

link to aws docs