Skip to content

[Feature] eksctl to export the resources it created in a json #8196

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

Open
dnyanesh-github opened this issue Feb 4, 2025 · 3 comments
Open
Labels
kind/feature New feature or request stale

Comments

@dnyanesh-github
Copy link

What feature/behavior/change do you want?

Why do you want this feature?

@dnyanesh-github dnyanesh-github added the kind/feature New feature or request label Feb 4, 2025
Copy link
Contributor

github-actions bot commented Feb 4, 2025

Hello dnyanesh-github 👋 Thank you for opening an issue in eksctl project. The team will review the issue and aim to respond within 1-5 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

@dnyanesh-github
Copy link
Author

If "eksctl" creates a json of the resources it created, then those can be leveraged for the subsequent pipeline stages for automation. For example, I wanted to filter out the private subnets eksctl created in the VPC, I had to explicitely search for them and write additional code to filter them out, however, if only I had the json, I could just use them right away. This information is so very cruicial for non EKS services like RDS or Elasticache deployment, because you want them deployed in your VPC with a subnet group created on a private subnet.

Copy link
Contributor

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.

@github-actions github-actions bot added the stale label Apr 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature New feature or request stale
Projects
None yet
Development

No branches or pull requests

1 participant