Hi David / @dcarrascal75,
Any reason why you chose to run a master reset and an init after restart?
The behavior you observe is expected when running a reset and init on master. In doing so, you wipe clean the configuration of the master and create new credentials for the cluster. Hence, the old worker is not able to join the cluster. An easy fix would be a reset and a join on the worker with the new token and hash values produced by the latest init of the master.
But why run reset at all? Assuming your nodes keep their IP addresses, and you permanently disabled swap on your nodes, a simple start of each node should bring up the k8s cluster as well.
If you are using Ubuntu 18.04 and the steps in our labs the kubelet process should be started by systemd. Basic flow is systemd -> kubelet -> kube-apiserver, etcd, kube-controller-manager. This would then start the rest of the pods as per what etcd has in the configuration file.
The boot process can take a bit. Run systemctl status kubelet to see if it is running. If it's not back after 2-3 minutes, use journalctl -u kubelet to see if there are other errors.
Let us know what you find,
The Kubernetes Scheduler repository on Github may be a good starting point to understand its main scheduling functions.
You should still look at the updates available and stay up to date on any security based ones
@parameswararao The error is a syntax issue for the curl request. Are you by chance using a Windows? If so, what terminal program? Different Windows terminals have different syntax requirements. This post on StackOverflow likely explains the necessary syntax changes for the standard Windows terminal: https://stackoverflow.com/questions/11834238/curl-post-command-line-on-windows-restful-service
Feel free to use the search feature of the forum, as most issues have been reported and solutioned already. Below are only a few discussions on this very same topic, but there are others:
I also suggest reading carefully the overview section of lab 3.1 because it presents helpful configuration options for inter-node networking.
I guess this area would be ok since you're dealing with that distro. I ran Mint for a long time as my go to, out of the box, it just works Linux for a long time.
What do you think so far?
My information may be old (I certified two years ago and I'm recertifying now) but you do not. Get the whole question right or no credit. My strategy is if I see a part I'm not confident about, I just skip the question.
We apologize for the inconvenience. Can you please send an email to [email protected], and explain the situation? They should be able to assist you.
Digital badges are issued every Monday for all completions in the previous week.