[EKS] [request]: new subnets should be displayed on eks console

Hello, one of our EKS clusters has run out of free IP addresses, so we created a new CIDR range and private subnets.

The main issue is that new subnets are not displayed on the EKS console.
When we contacted AWS support, they informed us that new subnets would not be visible in the console.

If that's the case, how can we determine/confirm which subnets our workloads are in if they're using new subnets that aren't visible on the EKS console?

Our workloads will be present in the extended network, despite the fact that the cluster network is limited to a few subnets.

When an audit or review occurs, it is extremely difficult to analyze the results.

Please take our feature request into consideration and implement it as soon as possible.

This is a public EKS product request rather than a repository change; no files, tests, or entry points are identified. Begin by reviewing how extended CIDR ranges and private subnets are represented in EKS, then define the console visibility and audit confirmation needed for the request to be complete.

Written by the indexing model from the issue text.