efs-provisioner should make FILE_SYSTEM_ID and AWS_REGION optional
mingfang opened this issue · 3 comments
The verification on startup fails when FILE_SYSTEM_ID and AWS_REGION is not set.
This verification should be skipped instead
I should be able to set the endpoint as an IP address to allow mounting from across a peering connection from another VPC/region as per AWS instructions for doing so.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
Thanks for reporting the issue!
This repo is no longer being maintained and we are in the process of archiving this repo. Please see kubernetes/org#1563 for more details.
If your issue relates to nfs provisioners, please create a new issue in https://github.com/kubernetes-sigs/nfs-ganesha-server-and-external-provisioner or https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner.
Going to close this issue in order to archive this repo. Apologies for the churn and thanks for your patience! 🙏