-
Notifications
You must be signed in to change notification settings - Fork 520
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
Issue with cluster installation #17
Comments
I am also facing this issue.. Error is `2023-05-17T03:01:33.463004756Z stderr F 2023-05-17 03:01:33.462 [ERROR][1] cni-installer/ : Unable to create token for CNI kubeconfig error=serviceaccounts "calico-cni-plugin" is forbidden: User "system:serviceaccount:kube-system:calico-node" cannot create resource "serviceaccounts/token" in API group "" in the namespace "kube-system" 2023-05-17T03:01:33.463036966Z stderr F 2023-05-17 03:01:33.462 [FATAL][1] cni-installer/ : Unable to create token for CNI kubeconfig error=serviceaccounts "calico-cni-plugin" is forbidden: User "system:serviceaccount:kube-system:calico-node" cannot create resource "serviceaccounts/token" in API group "" in the namespace "kube-system"` |
My issue has been resolved by using pod network cidr while initialising and updated same cidr in custom-resources.yml while adding network add-on. Now I’m able to join the nodes as well just make sure nodes are able to reach each other over network on 6443 port. |
Hi @lovemasta41 can you please share the solution? I have the same issue as you. Running Ubuntu 22.04 LTS on Virtualbox. Same issue on older Ubuntu 20.04 LTS |
@mihabez : follow below steps :-
|
The README.md file was updated with this helpful note just 3 days ago:
The videos aren't likely to have been updated yet as of this writing. In summary:
|
Hi Sander,
I was highly motivated to learn k8s from your course. I have 3 Ubuntu 22.04 instances running in AWS EC2 out of which on one of them I followed the steps mentioned in your course to set as control plane.
I used both the .sh files to install container runtime and Kube tools. After that I used sudo kubeadm init as mentioned in the video. Then performed steps to get cluster context. After that I simply did kubectl create -f cka/calico.yaml but my calico container is in crashloopbackoff state.
can you suggest if there are any changes I need to know to make it work ?
The text was updated successfully, but these errors were encountered: