AWS STS E2E tests cannot be run locally

[ben-taussig-solo]

Gloo Edge Product

Open Source

Gloo Edge Version

v1.16.0-beta6

Kubernetes Version

v1.25.3

Describe the bug

• AWS STS E2E tests cannot be run locally (at least, not easily)
• These tests require a JWT private key, which is used to sign an OIDC token, which mimics the WEB_IDENTITY_TOKEN_FILE that an EKS ServiceAccount would inject into the Gloo pod's filesystem
• A valid value for this private key is stored as a GCR secret and referenced when running e2e tests in CI
• However, I have not been able to figure out how to generate a working private key value that will allow me to run these tests on my local machine

Expected Behavior

• AWS STS E2E tests can be run without additional manual configuration on developer machines

Steps to reproduce the bug

1. Focus AWS STS E2E tests
2. make run-e2e-tests
3. Confirm that the tests fail due to the lack of a valid JWT Private Key

Additional Environment Detail

No response

Additional Context

No response