0

Steps: kubeadm init --apiserver-advertise-address= --pod-network-cidr=192.168.0.0/16 after executing above command it throw below issue

1-->[ERROR NumCPU]: the number of available CPUs 1 is less than the required 2
2-->[ERROR Mem]: the system RAM (966 MB) is less than the minimum 1700 MB

and re execute below comment kubeadm init --apiserver-advertise-address=172.31.92.76 --pod-network-cidr=192.168.0.0/16 --ignore-preflight-errors=NumCPU --ignore-preflight-errors=Mem it seem this error

This 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)


[preflight] Running pre-flight checks
        [WARNING NumCPU]: the number of available CPUs 1 is less than the required 2
        [WARNING Mem]: the system RAM (966 MB) is less than the minimum 1700 MB
error execution phase preflight: [preflight] Some fatal errors occurred:
        [ERROR FileAvailable--etc-kubernetes-manifests-kube-apiserver.yaml]: /etc/kubernetes/manifests/kube-apiserver.yaml already exists
        [ERROR FileAvailable--etc-kubernetes-manifests-kube-controller-manager.yaml]: /etc/kubernetes/manifests/kube-controller-manager.yaml already exists
        [ERROR FileAvailable--etc-kubernetes-manifests-kube-scheduler.yaml]: /etc/kubernetes/manifests/kube-scheduler.yaml already exists
        [ERROR FileAvailable--etc-kubernetes-manifests-etcd.yaml]: /etc/kubernetes/manifests/etcd.yaml already exists
[preflight] If you know what you are doing, you can make a check non-fatal with `--ignore-preflight-errors=...`
To see the stack trace of this error execute with --v=5 or higher
root@ip-172-31-92-76:/home/ubuntu#

how to over come this one

satheesh
  • 15
  • 5
  • **how to over come this one**, 1) create a new ec2 that satisfies the minimum requirements. 2) if you choose to continue, `kubeadm reset` might help. – P.... Dec 28 '22 at 19:26

0 Answers0