-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
"Setup Kubernetes on a Raspberry Pi Cluster easily the official way!" -- missing steps? #51
Comments
Helps toward hypriot#51 but not the complete fix
kube-dns seems to not work every time... I'm gonna reflash the SD cards, try again and see if 0.7.0 flannel makes any improvements |
More for hypriot#51
So copying the admin.conf was missing, fixed in the above commit too. Using 0.7.0 of flannel doesn't make any difference at least. But it's generally good not to just use arbitary commits from master Doesn't seem to matter if you do the |
But it seems things still actually error out :(
|
Plus node01 isn't ready...
|
@reedy Thanks you for your inspections, appreciate that you filed this issue and your PRs! Unfortunately, the two PRs don't seem to fix the issue. Please note that I won't have a further look at this problem and won't test it in the near future. Sorry that I can't provide support from my side! Though I am happy to include your PRs that improve the situation. Also during the blog posts, I encountered race conditions myself. Sad that they are still not fixed. Maybe @luxas can help out in this issue. |
@MathiasRenner this isn't related to that (the race conditions we're fixed in flannel v0.7.0) @reedy You should follow the new for kubeadm v1.6 commands:
Also flannel needs RBAC rules, please apply them as well. We maybe should point that out retroactively @MathiasRenner |
@luxas sure on the new v1.6 commands. Hence adding #53 which highlights them for other people so they need to add them, because I noticed that this guide didn't include them, but the 'installer' was spitting them out to be run. Which has been merged now. Thanks for both merges @MathiasRenner @luxas Where are these RBAC rules? Are you meaning https://github.com/coreos/flannel/blob/master/Documentation/kube-flannel-rbac.yml ? Is this as well as, or instead of kube-flannel.yml ? I note the -rbac version is newer than v0.7.0, so should be in a newer tagged release whenever that actually happens I did find kubernetes/kubeadm#143 suggesting other people are fixing up where necessary in the projects... Thanks! |
Ran into the same problem. Master
Node
Flannel worked for me:
alternatively Weave:
RBAC was the problem introduced with 1.6 |
So we do just need to add the rbac one first into the tutorial? |
Yes, rbac is enabled by default in version 1.6. http://blog.kubernetes.io/2017/04/rbac-support-in-kubernetes.html So this has to be added:
Providers of network plugins are called upon bundling rbac rules with their existing configuration. kubernetes/kubeadm#143 However, flannel does not include rbac. Therefore the additional rbac configuration. They may provide a bundled version soon. I have tested it with the latest The blog states version 0.7.0 for flannel. i did not explicitely test this version, nevertheless it should work. |
If using Kubernetes 1.6+ (with RBAC) I found I also had to use apply the Traefik RBAC instructions listed here https://github.com/containous/traefik/tree/master/examples/k8s/traefik-rbac.yaml (described at https://docs.traefik.io/user-guide/kubernetes/) I also had to tweak those once more by adding one line to include permission to I then had to update https://raw.githubusercontent.com/hypriot/rpi-traefik/master/traefik-k8s-example.yaml with lines to create the serviceAccount traefik-ingress-controller
|
So I'm going through https://blog.hypriot.com/post/setup-kubernetes-raspberry-pi-cluster/
After running
kubeadm init --pod-network-cidr 10.244.0.0/16
and thenkubeadm join --token
on the nodes... I go back to the master and runkubectl get nodes
, I getScrolling back up, I notice
Did some steps get missed out from your tutorial? Or did it get out of order?
If I run the copies...
But all my nodes are NotReady now... Follow the guide a bit further...
I guess doing some more commands forced it to do stuff?
Nodes stay ready... But the kube-flannel error all over the place and seemingly give up?
I also noticed
Using master is probably a bit temperamental...
I suppose, with the date of https://blog.hypriot.com/post/setup-kubernetes-raspberry-pi-cluster/ being Jan 11, and https://github.com/coreos/flannel/releases/tag/v0.7.0 being Jan 10... I guess you were using that. Rather than the various commits that are on master now flannel-io/flannel@v0.7.0...master
So, I think there's a versioning issue with flannel... I'll do a PR to swap it from master. And see about where to put the
kubectl get nodes
copy fixesThe text was updated successfully, but these errors were encountered: