-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Clarify need for bidirectional firewall rules for mount #20442
base: master
Are you sure you want to change the base?
Conversation
Example for Ubuntu, where 192.168.49.1 is the host interface and 192.168.49.2 is the minikube IP address: $ sudo ufw allow proto tcp from 192.168.49.1 to 192.168.49.2 port 22 $ sudo ufw allow proto tcp from 192.168.49.2 to 192.168.49.1 port 2222 $ minikube mount ./profiles:/var/lib/kubelet/seccomp/profiles --port=2222
The committers listed above are authorized under a signed CLA. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: glerb The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Welcome @glerb! |
Hi @glerb. Thanks for your PR. I'm waiting for a kubernetes 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. |
Can one of the admins verify this patch? |
Example for Ubuntu, where 192.168.49.1 is the host interface and 192.168.49.2 is the minikube IP address:
$ sudo ufw allow proto tcp from 192.168.49.1 to 192.168.49.2 port 22
$ sudo ufw allow proto tcp from 192.168.49.2 to 192.168.49.1 port 2222
$ minikube mount ./profiles:/var/lib/kubelet/seccomp/profiles --port=2222