Jeff Wenzbauer

> You received that error when you tried to assume the role? Yes, the action logged that error when it tried to assume the specified role in my GovCloud account....

Are those env vars being set by the action? You can see my complete workflow in my previous message. I am not setting env vars anywhere.

It appears that if I have this action occurring 2 times in a single workflow then the `region` set in the first step carries over into the 2nd step. Commenting...

This is probably obvious, but I confirmed that if I reverse the ordering of my steps that the same failure occurs in my non-govcloud role assumption. ```yaml name: "testing oidc"...

I just figured out that the region env var has nothing to do with the problem. Nulling out the session and access key env vars causes the error to not...

Luckily dumb bugs are usually easy to fix 👍

@richardhboyd any updates on getting a fix for this issue? Is the issue simply that [this `if` statement](https://github.com/aws-actions/configure-aws-credentials/blob/e21f7333e801ca751f058cc52de17f0ee6e1da6f/index.js#L276) is not properly checking if an access key is actually set?

> @eduard-t we think that this is an issue with field management since the alpha provider uses the Server Side Apply - https://kubernetes.io/docs/reference/using-api/server-side-apply/#field-management > > Since the field is being...

I should also note that the way I am currently installing kube2iam into my minikube is via helm with the following command: ```bash helm upgrade -i kube2iam --wait \ --set=extraArgs.base-role-arn=arn:aws:iam::${AWS_ACCOUNT_ID}:role/...

Would love to see this implemented MsTeams notifications are not currently usable for org-wide discussions. Having the ability to filter by label or category is a must or else the...