-
Notifications
You must be signed in to change notification settings - Fork 560
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
Revert to stunnel5 #1559
Revert to stunnel5 #1559
Conversation
Hi @dankova22. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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-sigs/prow repository. |
/ok-to-test |
86881cc
to
770f9d7
Compare
23893ca
to
534ec88
Compare
/test pull-aws-efs-csi-driver-unit |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dankova22, mskanth972 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 |
@dankova22 @mskanth972 looks like this reverts my PR, but it re-introduces security vulnerabilities back into efs-csi-driver. I noticed when implementing that PR that the Checking the version on a container running v2.1.3 confirms this:
|
Raised an issue with distro team to add stunnel5 to new distros aws/eks-distro-build-tooling#1591 |
@dankova22 The release note differences indicate that |
Revert to stunnel5 to fix mount issues