<!-- Thank you for opening this feature request! You are helping make eksctl a better project :) In order to help us process this request faster, please provide as much detail as possible. Before creating a feature request, please search existing issues to see if this request has already been made. If there is a similar feature request please up-vote it and/or add your comments to it instead. For more information on how to contribute to eksctl, please refer to our contributing docs. https://github.com/eksctl-io/eksctl/blob/main/CONTRIBUTING.md#opening-issues --> ### What feature/behavior/change do you want? <!-- Creating an EKS cluster alone is not enough all the time. You might have to deploy an RDS database or an Elasticache instance. If you want these to be connected to your cluster, we have to get the details about the cluster using other mechanisms like querying using AWS cli and filter out the information you need. Like I wanted to know the subnet ID's of only the private subnet eksctl created. Would it not be better, if eksctl dumps all this information(of-course if operator opted for it) in a JSON? This will help subsequent automation stages to automatically pick the values from the right source, rather than querying the cluster again for it. --> ### Why do you want this feature? <!-- I think I answered it in the previous question. -->
