Comments on How to Deploy Nginx Load Balancing on Kubernetes Cluster on Ubuntu 18.04 LTS
Kubernetes is a free and open-source container orchestration system that can be used to deploy and manage container. In this tutorial, we will learn how to setup Nginx load balancing with Kubernetes on Ubuntu 18.04.
2 Comment(s)
Comments
Hello, I'm getting this error message when trying to install and configure kubernetes on Ubuntu 16.
[etcd] Creating static Pod manifest for local etcd in "/etc/kubernetes/manifests"[wait-control-plane] Waiting for the kubelet to boot up the control plane as static Pods from directory "/etc/kubernetes/manifests". This can take up to 4m0s[kubelet-check] Initial timeout of 40s passed.Unfortunately, an error has occurred: timed out waiting for the conditionThis error is likely caused by: - The kubelet is not running - The kubelet is unhealthy due to a misconfiguration of the node in some way (required cgroups disabled)If you are on a systemd-powered system, you can try to troubleshoot the error with the following commands: - 'systemctl status kubelet' - 'journalctl -xeu kubelet'Additionally, a control plane component may have crashed or exited when started by the container runtime.To troubleshoot, list all containers using your preferred container runtimes CLI, e.g. docker.Here is one example how you may list all Kubernetes containers running in docker: - 'docker ps -a | grep kube | grep -v pause' Once you have found the failing container, you can inspect its logs with: - 'docker logs CONTAINERID'error execution phase wait-control-plane: couldn't initialize a Kubernetes cluster
Can I replace this "kubeadm init --pod-network-cidr=192.168.0.0/16 --apiserver-advertise-address=192.168.31.137" with another command as mentioned here.
kubeadm init --pod-network-cidr=192.168.0.0/16 --apiserver-advertise-address=192.168.31.137 --ignore-preflight-errors=
Will this help me solve the problem?
after i deploy cni and check kubectl get nodes my master status is notReady, any advice ?