kubernetes-sigs/aws-fsx-csi-driver

Support running e2e test on EKS

wongma7 opened this issue · 2 comments

wongma7 commented

/kind bug

What happened? The test fails because it tries to determine what security group to create the FSx file system in using kops-specific ec2 instance tags . https://github.com/kubernetes-sigs/aws-fsx-csi-driver/blob/master/tests/e2e/cloud.go#L46 The test should also check for EKS tags like https://github.com/kubernetes-sigs/aws-efs-csi-driver/blob/master/test/e2e/cloud.go#L215

https://github.com/kubernetes-sigs/aws-efs-csi-driver/blob/master/test/e2e/cloud.go#L215

What you expected to happen?

How to reproduce it (as minimally and precisely as possible)?

Anything else we need to know?:

Environment

  • Kubernetes version (use kubectl version):
  • Driver version:
k8s-triage-robot commented

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

wongma7 commented

/lifecycle frozen
/help-wanted