External-storage: [efs-provisioner] Support TLS encryption

Created on 10 Apr 2018 · 12Comments · Source: kubernetes-retired/external-storage

AWS have released an EFS mount helper that enables encryption in transit - https://aws.amazon.com/blogs/aws/new-encryption-of-data-in-transit-for-amazon-efs/

Using the "tls" option (where supported) be implemented and documented.

areawefs lifecyclrotten

Source

gtie

👍4

Most helpful comment

@nano2nd yup, in https://github.com/kubernetes-sigs/aws-efs-csi-driver which is kind of the evolution of the efs-provisioner.

Vlaaaaaaad on 9 Feb 2020

❤2

All 12 comments

Is any work being done on this as I have a requirement to enable TLS in order to use EFS in kube?

gregsidelinger on 3 Oct 2018

👍2

Not yet. I have not had the time to see how the mount helper works. Kubernetes is the one mounting shares, not the provisioner, and I don't think it's currently possible to tell it to mount with -t efs instead of -t nfs, so changes may be needed upstream.

wongma7 on 3 Oct 2018

If it proves impossible, something like an EFS CSI driver that bundles the mount helper and calls NodePublish with mount -t efs will need to be written. I wonder if anybody is working on that.

wongma7 on 3 Oct 2018

Amazon is writing a CSI driver https://github.com/aws/aws-efs-csi-driver

wongma7 on 10 Jan 2019

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

fejta-bot on 28 Apr 2019

/remove-lifecycle stale

ReillyTevera on 29 Apr 2019

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

fejta-bot on 28 Jul 2019

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten

fejta-bot on 27 Aug 2019

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

fejta-bot on 26 Sep 2019

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.