-
Notifications
You must be signed in to change notification settings - Fork 561
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
e2e: add elasticfilesystem:TagResource action #4272
Conversation
Signed-off-by: Marko Mudrinić <mudrinic.mare@gmail.com>
/assign @neolit123 |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: richardcase The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/cherry-pick release-1.5 |
@Ankitasw: new pull request created: #4324 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/cherry-pick release-2.0 |
@Ankitasw: new pull request created: #4335 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@Ankitasw: new pull request created: #4336 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
What type of PR is this?
/kind failing-test
What this PR does / why we need it:
We're trying to migrate the
periodic-cluster-api-provider-aws-e2e
job from Prow build cluster running on GKE to Prow build cluster running on EKS. As part of that, we added a new jobperiodic-cluster-api-provider-aws-e2e-eks-canary
. However, the job is consistently failing with:After some investigation, we found out that
efs-claim
PVC is not getting provisioned andefs-csi-controller
is logging to following error:After some additional investigation, we found out that adding
elasticfilesystem:TagResource
action to the node policy solves the problem. We're not 100% sure why that solves the issue, but upstream EFS CSI driver added it relatively recently as well: kubernetes-sigs/aws-efs-csi-driver@cd41c38We're also not 100% sure why we see this issue only in the new cluster, but we assume it might be related to the fact that we're using brand new boskos accounts, so maybe some account settings are different.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):xref kubernetes/k8s.io#5048
Checklist:
Release note:
cc @dims @pkprzekwas