Make spec.clusterName optional on `PodIdentityAssociation`

[joshuabaird]

Presently, a user has to specify a clusterName when creating a PodIdentityAssociation. This forces users to tailor their application manifests to specific clusters which complicates the management of the manifests when a user needs to deploy to X number of clusters.

If possible, clusterName should be optional, and the default value should be inferred from some other means within the controller or via a global configuration exposed by the controller.

While it may seem reasonable to expose this via configuration using something like an environment variable on the controller itself, the operator would still need to account for tailoring the controller manifests for specific clusters. This is probably a step in the right direction, but it would be ideal if there was a way to inform the controller of the cluster that it is running on (at least for EKS).

Using the EC2 metadata service was my first thought here, but it doesn't look like the cluster name is available via this service yet (although it's said to be "coming soon").

[eqe-aws]

Thanks for reaching out, we will take a look at possibly doing this in Q2.

[ack-bot]

Issues go stale after 180d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 60d of inactivity and eventually close. If this issue is safe to close now please do so with /close. Provide feedback via https://github.com/aws-controllers-k8s/community. /lifecycle stale

[ack-bot]

Stale issues rot after 60d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 60d of inactivity. If this issue is safe to close now please do so with /close. Provide feedback via https://github.com/aws-controllers-k8s/community. /lifecycle rotten