Skip to content
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

Unable to mount FSx as PV from a peered VPC #357

Open
satishpasumarthi opened this issue Oct 9, 2023 · 5 comments
Open

Unable to mount FSx as PV from a peered VPC #357

satishpasumarthi opened this issue Oct 9, 2023 · 5 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.

Comments

@satishpasumarthi
Copy link

/kind bug

What happened?
Hi, I've been looking into getting the PV and PVC setup for pods using the FSx in a peered account. I am unable to get the FSx mounted as PV:
Currently the aws-fsx-csi-driver helps with PV and PVC setup -- It takes dnsname into account for Mounting. But we can't mount FSx (peered vpc) using dnsname, but rather IP address of FSx should be used because we can't use dnsname for FSx (From a peered vpc)
What's the recommended way to accomplish this?
What you expected to happen?
Consume FSx ip address and mount the volume
How to reproduce it (as minimally and precisely as possible)?
Try PV and PVC for static FSx volume using the dnsname. The FSx volume should be from a peered VPC.

Anything else we need to know?:

Environment: AWS EKS

  • Kubernetes version (use kubectl version): 1.27
  • Driver version: 1.0
@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Oct 9, 2023
@satishpasumarthi
Copy link
Author

specifying ip address in the place of dnsname worked. Please improve the documentation.

@jonathonbyrdziak
Copy link

yea I had the same issue with DNS, just changed to the FSX -> ESI -> IP address and all worked well. you can find this IP from a simple nslookup in the same vpc.

changing to the IP address in the mount command worked perfectly

@paramjeet01
Copy link

In short , use IP instead of DNS.
Find this document helpful : https://docs.aws.amazon.com/fsx/latest/LustreGuide/mounting-on-premises.html

@k8s-triage-robot
Copy link

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Feb 2, 2024
@jacobwolfaws
Copy link
Contributor

/lifecycle frozen
docs update needed

@k8s-ci-robot k8s-ci-robot added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness.
Projects
None yet
Development

No branches or pull requests

6 participants