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
Minikube guide updates #16346
Minikube guide updates #16346
Conversation
Commit 7a3445db6e92da4ceec28c0e3523c351968878c8 does not contain "Signed-off-by". Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#developer-s-certificate-of-origin |
c1a0f07
to
aa6eb96
Compare
aa6eb96
to
e0fbc5a
Compare
e0fbc5a
to
cca09b8
Compare
cca09b8
to
6b1f8e3
Compare
Commit 12f089d757c683d701f730c4e568653ca09a440f does not contain "Signed-off-by". Please follow instructions provided in https://docs.cilium.io/en/stable/contributing/development/contributing_guide/#developer-s-certificate-of-origin |
--network-plugin=cilium
flag in minikube guide There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Cilium init script mounts the BPF fs if not already mounted so the manual step to mount BPF fs isn't required.
(Note that it could be worth having the above in the commit log of the revert patch. Not blocking, though.)
Looks good, thank you! Don't forget to sign-off :)
This reverts commit f3c90b8. Cilium init container mounts the BPF fs if it's not already mounted so the manual step to mount BPF fs isn't required. For details, check GH cilium#16346. Signed-off-by: Aditi Ghag <aditi@cilium.io>
6b1f8e3
to
7584e4f
Compare
@qmonnet Updated the commit description for the reverted commit. Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
I'm ambivalent about documenting the minikube --cni=cilium ...
flag or not, seems like we have legitimate reasons not to recommend the user to use it so it'd be simpler to omit the instruction. That said it's not a big deal to also just let the user know like this. However I think if we do so, we should move the note inside the group tab for minikube users rather than instruct all users about this, even if they've clicked one of the other group tabs (why would cloud or kind users need to be told about a minikube feature?).
From minikube v1.12.1+, the flag passed to `minikube start` command will deploy quick-install.yaml automatically. However, it currently installs v1.8 by default so add a note regarding this. Signed-off-by: Aditi Ghag <aditi@cilium.io>
7584e4f
to
4c33568
Compare
Add a note about
--cni=cilium
flag that can automatically install Cilium. However, it installs v1.8 by default so add a note regarding this.Cilium init script mounts the BPF fs if not already mounted so the manual step to mount BPF fs isn't required. Let's double check -
ebpf-mount
is the init container that mounts the BPF fs. Here is the relevant code in cilium/cli - https://github.com/cilium/cilium-cli/blob/master/install/install.go#L685Fixes: #16324