kubernetes
Clarify need for bidirectional firewall rules for mount
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.
- :white_check_mark: login: glerb / name: Patrick Hagan (02ac5561f8e98f02626570a0daf1fa59a01263ab, 13d6bd6f4b4c323c05b47eb7ee5c3971c076197b, 4bfa1cc24e2b3e373dfbc5ad1a2d1a1c2eebae4c)
![linux-foundation-easycla[bot] avatar](https://avatars.githubusercontent.com/in/17893?v=4 "Published by a pub.dev verified publisher"){kind=small}
Welcome @glerb!
It looks like this is your first PR to kubernetes/minikube 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.
You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.
You can also check if kubernetes/minikube has its own contribution guidelines.
You may want to refer to our testing guide if you run into trouble with your tests not passing.
If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!
Thank you, and welcome to Kubernetes. :smiley:
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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
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.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: glerb, medyagh
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [medyagh]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
kvm2 driver with docker runtime
┌────────────────┬──────────┬────────────────────────┐
│ COMMAND │ MINIKUBE │ MINIKUBE ( PR 20442 ) │
├────────────────┼──────────┼────────────────────────┤
│ minikube start │ 52.4s │ 52.5s │
│ enable ingress │ 15.4s │ 15.8s │
└────────────────┴──────────┴────────────────────────┘
Times for minikube start: 52.9s 50.0s 53.3s 52.4s 53.2s Times for minikube (PR 20442) start: 50.7s 54.4s 52.2s 52.7s 52.4s
Times for minikube ingress: 15.6s 17.0s 14.6s 15.0s 14.6s Times for minikube (PR 20442) ingress: 15.1s 14.7s 15.5s 15.1s 18.6s
docker driver with docker runtime
┌────────────────┬──────────┬────────────────────────┐
│ COMMAND │ MINIKUBE │ MINIKUBE ( PR 20442 ) │
├────────────────┼──────────┼────────────────────────┤
│ minikube start │ 24.3s │ 24.8s │
│ enable ingress │ 13.2s │ 13.3s │
└────────────────┴──────────┴────────────────────────┘
Times for minikube start: 23.5s 24.8s 23.7s 24.3s 25.4s Times for minikube (PR 20442) start: 23.8s 22.4s 26.8s 26.5s 24.3s
Times for minikube (PR 20442) ingress: 13.3s 12.8s 13.8s 13.8s 12.8s Times for minikube ingress: 13.3s 12.9s 13.8s 12.3s 13.8s
docker driver with containerd runtime
┌────────────────┬──────────┬────────────────────────┐
│ COMMAND │ MINIKUBE │ MINIKUBE ( PR 20442 ) │
├────────────────┼──────────┼────────────────────────┤
│ minikube start │ 23.6s │ 24.8s │
│ enable ingress │ 23.0s │ 22.8s │
└────────────────┴──────────┴────────────────────────┘
Times for minikube start: 23.2s 22.3s 25.5s 22.4s 24.7s Times for minikube (PR 20442) start: 21.7s 25.4s 25.2s 25.1s 26.5s
Times for minikube ingress: 22.8s 22.8s 22.8s 23.8s 22.8s Times for minikube (PR 20442) ingress: 22.8s 22.8s 22.8s 22.8s 22.8s
@glerb: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| pull-minikube-integration | 4bfa1cc24e2b3e373dfbc5ad1a2d1a1c2eebae4c | link | true | /test pull-minikube-integration |
| integration-none-docker-linux-x86-64 | 4bfa1cc24e2b3e373dfbc5ad1a2d1a1c2eebae4c | link | true | /test integration-none-docker-linux-x86-64 |
| integration-docker-containerd-linux-x86-64 | 4bfa1cc24e2b3e373dfbc5ad1a2d1a1c2eebae4c | link | true | /test integration-docker-containerd-linux-x86-64 |
| integration-kvm-crio-linux-x86-64 | 4bfa1cc24e2b3e373dfbc5ad1a2d1a1c2eebae4c | link | true | /test integration-kvm-crio-linux-x86-64 |
| integration-docker-crio-linux-x86-64 | 4bfa1cc24e2b3e373dfbc5ad1a2d1a1c2eebae4c | link | true | /test integration-docker-crio-linux-x86-64 |
| integration-docker-docker-linux-x86-64 | 4bfa1cc24e2b3e373dfbc5ad1a2d1a1c2eebae4c | link | true | /test integration-docker-docker-linux-x86-64 |
| integration-kvm-docker-linux-x86-64 | 4bfa1cc24e2b3e373dfbc5ad1a2d1a1c2eebae4c | link | true | /test integration-kvm-docker-linux-x86-64 |
| integration-kvm-containerd-linux-x86-64 | 4bfa1cc24e2b3e373dfbc5ad1a2d1a1c2eebae4c | link | true | /test integration-kvm-containerd-linux-x86-64 |
| integration-docker-docker-linux-arm64 | 4bfa1cc24e2b3e373dfbc5ad1a2d1a1c2eebae4c | link | true | /test integration-docker-docker-linux-arm64 |
| integration-docker-docker-linux-x86 | 4bfa1cc24e2b3e373dfbc5ad1a2d1a1c2eebae4c | link | true | /test integration-docker-docker-linux-x86 |
| integration-kvm-containerd-linux-x86 | 4bfa1cc24e2b3e373dfbc5ad1a2d1a1c2eebae4c | link | true | /test integration-kvm-containerd-linux-x86 |
| integration-kvm-docker-linux-x86 | 4bfa1cc24e2b3e373dfbc5ad1a2d1a1c2eebae4c | link | true | /test integration-kvm-docker-linux-x86 |
| integration-docker-docker-linux-arm | 4bfa1cc24e2b3e373dfbc5ad1a2d1a1c2eebae4c | link | true | /test integration-docker-docker-linux-arm |
| integration-docker-crio-linux-x86 | 4bfa1cc24e2b3e373dfbc5ad1a2d1a1c2eebae4c | link | true | /test integration-docker-crio-linux-x86 |
| integration-none-docker-linux-x86 | 4bfa1cc24e2b3e373dfbc5ad1a2d1a1c2eebae4c | link | true | /test integration-none-docker-linux-x86 |
| integration-kvm-crio-linux-x86 | 4bfa1cc24e2b3e373dfbc5ad1a2d1a1c2eebae4c | link | true | /test integration-kvm-crio-linux-x86 |
| integration-docker-containerd-linux-x86 | 4bfa1cc24e2b3e373dfbc5ad1a2d1a1c2eebae4c | link | true | /test integration-docker-containerd-linux-x86 |
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.
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. I understand the commands that are listed here.