인프런 커뮤니티 질문&답변

kubeadm init 설정하려고 ip 대역 다 변경해봐도 아래와 같은 오류가 생성되는거 같은데 어떻게 해야하나요?

 kubeadm init --pod-network-cidr=20.96.0.0/12 --apiserver-advertise-address=192.168.137.30

I0314 13:20:35.895203   74484 version.go:252] remote version is much newer: v1.20.4; falling back to: stable-1.19

W0314 13:20:36.441185   74484 configset.go:348] WARNING: kubeadm cannot validate component configs for API groups [kubelet.config.k8s.io kubeproxy.config.k8s.io]

[init] Using Kubernetes version: v1.19.8

[preflight] Running pre-flight checks

        [WARNING SystemVerification]: this Docker version is not on the list of validated versions: 20.10.5. Latest validated version: 19.03

error execution phase preflight: [preflight] Some fatal errors occurred:

        [ERROR Port-10259]: Port 10259 is in use

        [ERROR Port-10257]: Port 10257 is in use

        [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

        [ERROR Port-10250]: Port 10250 is in use

[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