When one uses the IAM Roles for Service Accounts feature for assigning an IAM role with S3 access to a pod, EKS mounts an auth token and sets environment variables in the pod. Everything works fine except cloning from S3 archive.
Please add AWS_ROLE_ARN, AWS_WEB_IDENTITY_TOKEN_FILE variables to WAL-G clone environment, "/run/etc/wal-e.d/env-clone", same as in https://github.com/zalando/spilo/pull/769.
mungo312
commented
5 months ago
When one uses the IAM Roles for Service Accounts feature for assigning an IAM role with S3 access to a pod, EKS mounts an auth token and sets environment variables in the pod. Everything works fine except cloning from S3 archive. Please add AWS_ROLE_ARN, AWS_WEB_IDENTITY_TOKEN_FILE variables to WAL-G clone environment, "/run/etc/wal-e.d/env-clone", same as in https://github.com/zalando/spilo/pull/769.
Same request for STANDBY.