You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I used the instructions here https://snapcraft.io/eks
I additionally added the user permissions as in this link. There was no problem with joining two nodes. But the third node does not join (as seen by running sudo eks kubectl get nodes (attached terminal screenshot). There is no error. I tried multiple times but the result is the same (even with restarting the node).
The text was updated successfully, but these errors were encountered:
There was no problem with joining two nodes. But the third node does not join (as seen by running sudo eks kubectl get nodes (attached terminal screenshot).
I am not sure I understand the issue. I see in the attached output three "Ready" nodes.
@ktsakalozos
Hi,
I created 4 nodes. I joined nodes 2 and 3 to the 1st node. When I did eks join for the fourth node, there was no error message (the first part of screenshot). But the node cannot be seen with the eks kubectl get nodes command (the second part of the screenshot).
Update today: I removed eks on all VMs and reinstalled it again today using exactly the same procedure and sequence. I repeated the eks join commands and now I see all the four nodes. So I am not sure where exactly the problem was.
Please run
![Screenshots](https://user-images.githubusercontent.com/3962573/124388217-367fd900-dce2-11eb-92a9-53ded465fd17.png)
microk8s inspect
and attach the generated tarball to this issue.inspection-report-worker.tar.gz
inspection-report-control.tar.gz
I used the instructions here https://snapcraft.io/eks
I additionally added the user permissions as in this link. There was no problem with joining two nodes. But the third node does not join (as seen by running
sudo eks kubectl get nodes
(attached terminal screenshot). There is no error. I tried multiple times but the result is the same (even with restarting the node).The text was updated successfully, but these errors were encountered: