[EKS] [request]: Amazon EKS (v1.23+) allows customer to create PVC with the default StorageClass provisioner instead of the Amazon EBS CSI provisioner.

### 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**
Amazon EKS (v1.23+) allows the customer to create PVC with the default StorageClass provisioner instead of using the Amazon EBS CSI provisioner when no `storageClassName` is set.

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

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**

On the new Amazon EKS cluster versions 1.23 and 1.24. When a new PVC is created with no specific `storageClassName`, Amazon EKS instructs the PVC to use the Amazon EBS CSI provisioner instead of the default StorageClass provisioner. It happens even when no Amazon EBS CSI driver is installed on the cluster.

It puts our product deployment into the pending state with no apparent error message in the events.

**Are you currently working around this issue?**

How are you currently solving this problem?

[Workaround solution for our product](https://docs.kubecost.com/troubleshooting/troubleshoot-install#issue-waiting-for-a-volume-to-be-created-either-by-external-provisioner-ebs.csi.aws.com-or-manually)

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

Suggestions:
- Change the Amazon EKS cluster version 1.23+ to the default storage class provisioner instead of the Amazon EBS CSI provisioner. The workaround solution to install Amazon EBS CSI driver may not work for the use case where customers want to use their own custom StorageClass
- Update Amazon EKS troubleshooting [docs](https://docs.aws.amazon.com/eks/latest/userguide/cost-monitoring.html) to add our workaround solution and change the default version to our latest version e.g: 1.99.0

**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.)

N/A

Start by reviewing the reported PVC behavior on Amazon EKS 1.23+ and the linked EKS troubleshooting documentation. Compare the requested default StorageClass behavior with the documented EBS CSI workaround; the issue is done when the EKS behavior is corrected or the troubleshooting guidance clearly covers this case.

Written by the indexing model from the issue text.