Operator UI not working in EKS IRSA mode

Please, answer some short questions which should help us to understand your problem / question better?

• Which image of the operator are you using? registry.opensource.zalan.do/acid/postgres-operator:v1.10.1
• Where do you run it - cloud or metal? Kubernetes or OpenShift? AWS EKS
• Are you running Postgres Operator in production? yes
• Type of issue? Bug report/feature request

Currently the AWS EKS IRSA authentication method is more mature from a security standpoint since the it does not require access keys to be provided, but instead allows the pod's ServiceAccount to assume an IAM role temporarily.

While I got it to work with the operator itself (cluster pods are able to upload physical basebackups to S3 with wal-g), the operator UI still only ships with wal-e for querying available backups, which needs explicit access keys to be provided and consequently does not work with IRSA. While cloning might still work by supplying the UUID, cluster name and timestamp in the CRD instance, it would be very helpful it the operator UI would also support IRSA.

Start with the operator UI's wal-e backup-query path and the AWS EKS IRSA documentation linked in the issue. Compare it with the existing operator and wal-g setup that works for cluster pods; done means the UI can query available backups under IRSA without requiring explicit access keys.