Welcome to the Linux Foundation Forum!

lab 4.2

sergeizak
sergeizak Posts: 20
in LFS258 Class Forum

At the end of lab 4.2, i started getting

The connection to the server k8smaster:6443 was refused - did you specify the right host or port?

What went wrong?

Comments

  • sergeizak
    sergeizak Posts: 20

    i ran kubectl create -f hog2.yaml (step 10 in lab 4.4)
    and then got the error on getting deployments

    kubectl get deployments --all-namespaces

    it happened abruptly, all of a sudden..

    My VMs are n1-standard-2 (2 vCPUs, 7.5 GB memory)

  • chrispokorni
    chrispokorni Posts: 2,606
    edited August 2020

    Another solution would be to restart the kubelet service and try to delete the hog and hog2 deployments immediately after, but before the kube-apiserver crashes again. The kubelet restart forces the apiserver to restart as well, and you may have a short window to run kubectl commands.

    Regards,
    -Chris

  • sergeizak
    sergeizak Posts: 20

    i decided to re-create the cluster. Can you help me locate the instructions? I recall a video from Tim walking through the steps of provisioning master and worker nodes in GCP. Can't find it anymore. Thx!

  • fcioanca
    fcioanca Posts: 2,614

    @sergeizak Please check the intro chapter towards the end, marked Important. You will find the video there

  • sergeizak
    sergeizak Posts: 20

    https://trainingportal.linuxfoundation.org/learn/course/kubernetes-fundamentals-lfs258/course-introduction/course-information?page=7

  • angusg
    angusg Posts: 2

    Make sure the name "k8smaster" will resolve, try a simple "ping, if not fix that, see if your hosts file settings are still correct. If that is working then next make sure you have an environment value for "KUBECONFIG", echo $KUBECONFIG if this is not set that a quick fix is to set it again using "export KUBECONFIG="$HOME/.kube/config". Add this to your .bashrc if not there already.
    hth

  • maybel
    maybel Posts: 45

    Hi guys, I wonder if I did something wrong because lab 4.3.10 should result in the following:
    I0927 21:09:23.514921 1 main.go:26] Allocating "0" memory, in "4ki" chunks, with a 1ms
    ,→ sleep \
    between allocations
    I0927 21:09:23.514984 1 main.go:39] Spawning a thread to consume CPU
    I0927 21:09:23.514991 1 main.go:39] Spawning a thread to consume CPU
    I0927 21:09:23.514997 1 main.go:29] Allocated "0" memory

    and I got:
    student@cp:~$ kubectl logs hog-559d5585fd-jzvsf
    I0320 18:15:00.416686 1 main.go:26] Allocating "950.Mi" memory, in "100Mi" chunks, with a 1s sleep between allocations
    I0320 18:15:00.416797 1 main.go:39] Spawning a thread to consume CPU
    I0320 18:15:00.416815 1 main.go:39] Spawning a thread to consume CPU
    I0320 18:15:13.583421 1 main.go:29] Allocated "950.Mi" memory
    student@cp:~$ Connection to 34.77.248.77 closed by remote host.

    The hog.yaml file was modified and to me, my results make sense but the pdf results are different than mine.

  • maybel
    maybel Posts: 45

    I change my view; it doesn't make sense because of my resource limits.

    resources:
    limits:
    cpu: "1"
    memory: "4Gi"
    requests:
    cpu: "0.5"
    memory: "500Mi"
    Then I don't understand how it is happening.

Categories

Upcoming Training