Section 2.1.5 "cannot get resource" Error thrown during $ sudo kubeadm join...

Hello,

To answer your second post first, you will need to use the same version of software on both nodes. Were you using 1.12.1 on both nodes before when the join failed? If you add a -v-10 to the join command you can see even more output which may help find the error.
Please show the kubeadm init command on the master node and the kubeadm join command on the worker node to help troubleshoot the issue. Also any errors that are in the init or join commands would help.

Regards,

There is a feature (which I just found) that the init process looks for an uses the newest version of software, regardless of what was installed. Once the 1.13 software was released the control plane no longer matches. This issues would come up every time a new version of software is released.
The fix is to include this into the command:

kubeadm init --kubernetes-version 1.12.1 --pod-network-cidr 192.168.0.0/16

The process would also work if all software were on 1.13, until 1.14 is available.

Regards,

I finally decided to use the suggested approach, then I created 2 VM on Google Cloud and configured the cluster. It works just fine but deployed the first pod (basic.yaml) I'm not able to connect to it after configuring the containerPort.
Doing a kubectl get pod -o wide I get :

NAME       READY   STATUS    RESTARTS   AGE   IP                NODE           NOMINATED NODE   READINESS GATES
basicpod   1/1     Running   0          36m   192.168.184.130   lft-minion-1   <none>           <none>

And doing a kubectl describe pod basicpod I get:

Containers:
  webcont:
    Container ID:   docker://f7acff6efc34df9cb328824f1f74c1a14596c127fd64d800658d63794145463f
    Image:          nginx
    Image ID:       docker-pullable://nginx@sha256:5d32f60db294b5deb55d078cd4feb410ad88e6fe77500c87d3970eca97f54dba
    Port:           80/TCP
    Host Port:      0/TCP
    State:          Running
      Started:      Thu, 20 Dec 2018 10:24:13 +0000
    Ready:          True
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-9zqf4 (ro)
Conditions:
  Type              Status
  Initialized       True 
  Ready             True 
  ContainersReady   True 
  PodScheduled      True 
Volumes:
  default-token-9zqf4:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-9zqf4
    Optional:    false
QoS Class:       BestEffort
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
                 node.kubernetes.io/unreachable:NoExecute for 300s
Events:
  Type    Reason     Age   From                   Message
  ----    ------     ----  ----                   -------
  Normal  Scheduled  35m   default-scheduler      Successfully assigned default/basicpod to lft-minion-1
  Normal  Pulling    35m   kubelet, lft-minion-1  pulling image "nginx"
  Normal  Pulled     35m   kubelet, lft-minion-1  Successfully pulled image "nginx"
  Normal  Created    35m   kubelet, lft-minion-1  Created container
  Normal  Started    35m   kubelet, lft-minion-1  Started container
 

Then, everything seems ok but I can't connect to 192.168.184.130 doing curl http://192.168.184.130

Hi @kozdog ,
In step 3 of the Lab, running cat against the k8sSecond.sh script provides an output of the entire script, all the commands that the script will run thru in order to initialize Kubernetes on the second node. The lines below the cat line are just a snippet of the output.
In step 4 however, you are running the shell script, which then executes on your behalf all the commands in it, including the one highlighted above.
Regards,
-Chris