[EKS] [eks-pod-identity]: How to confirm whether the pod identity associations are ready using the API

Tell us about your request.
EKS Pod Identity associations only apply to newly created pods and do not automatically update existing pods; to grant access to existing pods, you need to re-deploy them with the associated service account to leverage the new IAM role permissions provided by the Pod Identity association.

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?
When we add an association to our pods, the association shows that it is created, and the pod rolls to get the pod identity environment variables; however, they come up without the credentials and remain in CrashLoopBackOff, requiring us to roll them again to get the pod identity environment variables. We can't see a way to tell whether the pod identity associations are ready using the API and want to know if there is a way to confirm that they are ready through the API. We followed the exact steps mentioned in the documentation, https://docs.aws.amazon.com/eks/latest/userguide/pod-id-association.html.

Are you currently working around this issue?

The pod identity association works once the pod is restarted. It will enter CrashLoopBackOff and not have the environment variables on first start. I would like to give the command the proper time to bring the association fully up before rolling the pods to get the new credentials from the agent. How can I assure this happens? Are there settings I can utilize with the agent to make sure the variables get there, or are there commands I can issue through the CLI? There aren't any useful attributes output. I can see that the CLI returns:
https://awscli.amazonaws.com/v2/documentation/api/latest/reference/eks/describe-pod-identity-association.html#output

Let's say we create the pod association and then immediately roll the pods; the EKS pod identity association create command will return as successful, and the pods will start to be re-rolled. The issue is the command finishes, and it seems that the association isn't fully created, because when the pods roll, the environment variables aren't there. If I were to come back and roll the pods manually, the proper environment variables would be there, and it would work, but I need to know when the association is fully done creating.

Additional context
amazon-eks-pod-identity-webhook is installed.

The issue provides no repository files, tests, or entry points to start from. Read the linked EKS Pod Identity association and describe-pod-identity-association API documentation; done would be an API-visible way to determine readiness before restarting pods.

Written by the indexing model from the issue text.