EKS Fargate [Bug]: Containers running in Fargate cannot get their own metrics from the kubelet

### 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? Containers running in Fargate cannot get their own metrics from the kubelet

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

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem.

Currently, when trying to use curl or when running the metrics server calls against https://:10250/metrics/resource will fail, in both cases it is a, connection refused error. Below is an example from the metrics server.

```
E0804 18:26:43.486945 1 scraper.go:140] "Failed to scrape node" err="Get \"https://192.168.165.181:10250/metrics/resource\": dial tcp 192.168.165.181:10250: connect: connection refused" node="fargate-ip-192-168-165-181.ec2.internal"
```

The goal of this feature request/bug report would be to allow a Fargate pod to know it's own kubelet metrics.

**Are you currently working around this issue?**
How are you currently solving this problem? I do not see a workaround.

**Additional context**
Anything else we should know?

This mainly impact the metrics-server application as far as I can tell. The reasons for this are detailed [here](https://stackoverflow.com/a/67091094) and this issue was previously raised with the metrics-server GitHub [here](https://github.com/kubernetes-sigs/metrics-server/issues/694). I was unable to find this issue raised here so I am putting it here to give this issue more visibility and making it easier to search.

**Attachments**
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

No repository files or tests are identified in the issue. Start by reviewing the metrics-server issue 694 and the reported Fargate kubelet endpoint at :10250/metrics/resource. Done means a Fargate pod can access its own kubelet resource metrics and metrics-server can scrape them without a connection-refused error.

Written by the indexing model from the issue text.