[EMR on EKS] [Issue]: Throws SparkException: No pod was found named * in the cluster in the namespace * (this was supposed to be the driver pod.)

### 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**
This is an issue. According to this [documentation](https://docs.aws.amazon.com/emr/latest/EMR-on-EKS-DevelopmentGuide/jobruns-using-retry-policies.html), EMR jobs on EKS with versions 6.9.0 and later supports the user to configure retry policy which makes long-running Spark streaming jobs more resilient to failures. The documentation says

> Driver pod names follow the format spark-\-driver-\. The same random-suffix is added to the executor pod names that the driver spawns. When you use this random-suffix, you can find logs for a driver and its associated executors. The random-suffix is only present if the [retry policy is enabled](https://docs.aws.amazon.com/emr/latest/EMR-on-EKS-DevelopmentGuide/jobruns-using-retry-policies.html#retry-config) for the job; otherwise, the random-suffix is absent.

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

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
* When I execute the job with retry policy with maximum attempts of 5. My driver pods are failing with the following error
`org.apache.spark.SparkException: No pod was found named spark--driver in the cluster in the namespace (this was supposed to be the driver pod.)`. But it should be clearly trying to find driver pod with the following name `spark--driver-` since this is job with retry policy configuration
* I'm trying to trigger the EMR on EKS job directly from the step function using the Task `arn:aws:states:::emr-containers:startJobRun.sync`

**Are you currently working around this issue?**
No work around found yet

**Additional context**
* Let me know if I should create this issue in a more relevant page.

**Attachments**

Start with the linked EMR on EKS retry-policy documentation and the Step Functions entry point arn:aws:states:::emr-containers:startJobRun.sync. Reproduce the reported driver-pod lookup with retry enabled and compare the documented random-suffix naming with the exception. Done means the service locates the retry-specific driver pod or clearly documents the supported behavior; no repository file or test is identified in the issue.

Written by the indexing model from the issue text.