[eks] [request]: ability to provide pod restart from AWS console

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**
What do you want us to build?

**Which service(s) is this request for?**
This could be EKS

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Need option to rollout restart of deployments or restarting pod from AWS UI console because we use private cluster it cannot be accessed outside of VPC and its very hard to restart with Support access

**Are you currently working around this issue?**
currently we created one micro instance inside VPC which connects to EKS controlplane and do rollout restart of all deployments which is risky as it need some elevated privileges

**Additional context**

**Attachments**

The request concerns restarting pods or rolling out deployments through the AWS console for private EKS clusters. No repository files, tests, or entry points are mentioned; start by reviewing the EKS console workflow and private-cluster access constraints. Done should provide a defined, supported console-based restart capability without requiring an in-VPC instance with elevated privileges.

Written by the indexing model from the issue text.