CKAD course script LFD259V2023-12-13SOLUTIONS.tar.xz does not exist

arpitsharma14

arpitsharma14

https://cm.lf.training/LFD259/LFD259V2023-12-13SOLUTIONS.tar.xz

Flavia

Please check the link, as it is missing the underscores (there is a note in the course under the wget command that warns about the copy/paste behavior).

chrispokorni

Hi @arpitsharma14,

The discussion was moved to the correct LFD259 forum; it was incorrectly posted in the LFS260 forum.

Regards,
-Chris

arpitsharma14

i am not able to connect worker node to master node

getting the error below:

ubuntu@ip-172-31-88-44:~$ sudo kubeadm join 172.31.92.198:6443 --token 7i3xij.1pf0136a6r3xkizr --discovery-token-ca-cert-hash sha256:32bf354f01be488b30ec583ae4d608ca0b238a55ef4778d5c2e3399a3621bb21
[preflight] Running pre-flight checks

error execution phase preflight: couldn't validate the identity of the API Server: Get "https://172.31.92.198:6443/api/v1/namespaces/kube-public/configmaps/cluster-info?timeout=10s": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)
To see the stack trace of this error execute with --v=5 or higher

Master config:

kubectl config view
apiVersion: v1
clusters:

• cluster:
  certificate-authority-data: DATA+OMITTED
  server: https://172.31.92.198:6443
  name: kubernetes
  contexts:

• context:
  cluster: kubernetes
  user: kubernetes-admin
  name: kubernetes-admin@kubernetes
  current-context: kubernetes-admin@kubernetes
  kind: Config
  preferences: {}
  users:

• name: kubernetes-admin
  user:
  client-certificate-data: DATA+OMITTED
  client-key-data: DATA+OMITTED

But on. worker node i am getting this error ::

ubuntu@ip-172-31-88-44:~$ kubectl get nodes
E0110 05:52:47.493279 14982 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
E0110 05:52:47.493641 14982 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
E0110 05:52:47.495078 14982 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
E0110 05:52:47.495417 14982 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
E0110 05:52:47.496871 14982 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp 127.0.0.1:8080: connect: connection refused
The connection to the server localhost:8080 was refused - did you specify the right host or port?

arpitsharma14

@fcioanca @chrispokorni Please see the error above for worker node, its not able to connect to master. It dosn't even gives output for kubectl get nodes

chrispokorni

Hi @arpitsharma14,

If you pay close attention to the lab guide, the kubectl command is presented to work from the control plane node and it is not configured to work on the worker node, hence the error it returns is expected.

When provisioning the two AWS EC2 instances did you happen to follow the video tutorial from the introductory chapter? It presents essential network, firewall, and VM configuration details that are critical requirements for the successful operation of the Kubernetes cluster.

Regards,
-Chris

arpitsharma14

Yes i have followed the steps, all communication is open for the both the instances.

arpitsharma14

chrispokorni

Hi @arpitsharma14,

Please pay close attention to the video tutorial and follow it carefully.

Your inbound rules block most traffic required by Kubernetes, allowing only the TCP protocol to three distinct port numbers.

For the purpose of the lab environment all inbound traffic should be allowed, as per the demo video in the introductory chapter.

Regards,
-Chris

arpitsharma14

The video tutorial is on old, user interface and options have changed even when i am creating security group and while updting rules. It does not allow me to edit it.

arpitsharma14

arpitsharma14

@chrispokorni how can i get the command back, the out file has been deleted since i ran the command again.

chrispokorni

Hi @arpitsharma14,

Once you stop the EC2 instances and the rules are no longer actively protecting instances, you should be able to edit the SG rules and update them as desired.

how can i get the command back, the out file has been deleted since i ran the command again

It is not clear what command you are trying to get back, and what command you ran again.

Regards,
-Chris