vagrant up 오류 문의

회사 내부망이라서 인증오류가 발생한 듯 보이네요.더이상 시간을 끌 수 없어서 포기하고 ec2에 동일한 환경으로 구축했습니다.대시보드 접속까지 확인했습니다.도움 감사합니다.강의 보면서 추가 질문 드리도록 하겠습니다.

vagrant up 오류 문의

알려주신 명령으로 삭제 / 생성했습니다. 그리고 node2로 확인되어 node2에서 명령 실행했으나 에러가 발생하네요[root@k8s-master ~]# kubectl get pods -A -o wide NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES kube-system coredns-78fcd69978-d42t6 0/1 Pending 0 97m kube-system coredns-78fcd69978-h7pb5 0/1 Pending 0 97m kube-system etcd-k8s-master 1/1 Running 1 (62m ago) 97m 192.168.56.30 k8s-master kube-system kube-apiserver-k8s-master 1/1 Running 1 (62m ago) 97m 192.168.56.30 k8s-master kube-system kube-controller-manager-k8s-master 1/1 Running 1 (62m ago) 97m 192.168.56.30 k8s-master kube-system kube-proxy-5sgbs 1/1 Running 1 (62m ago) 97m 192.168.56.30 k8s-master kube-system kube-proxy-p464f 1/1 Running 1 (62m ago) 79m 192.168.56.32 k8s-node2 kube-system kube-proxy-xb4h6 1/1 Running 1 (62m ago) 79m 192.168.56.31 k8s-node1 kube-system kube-scheduler-k8s-master 1/1 Running 1 (62m ago) 97m 192.168.56.30 k8s-master tigera-operator tigera-operator-cffd8458f-srgq5 0/1 ErrImagePull 0 42s 192.168.56.32 k8s-node2 [root@k8s-master ~]# kubectl get pods -A -o wide NAMESPACE NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES kube-system coredns-78fcd69978-d42t6 0/1 Pending 0 98m kube-system coredns-78fcd69978-h7pb5 0/1 Pending 0 98m kube-system etcd-k8s-master 1/1 Running 1 (63m ago) 98m 192.168.56.30 k8s-master kube-system kube-apiserver-k8s-master 1/1 Running 1 (63m ago) 98m 192.168.56.30 k8s-master kube-system kube-controller-manager-k8s-master 1/1 Running 1 (63m ago) 98m 192.168.56.30 k8s-master kube-system kube-proxy-5sgbs 1/1 Running 1 (63m ago) 98m 192.168.56.30 k8s-master kube-system kube-proxy-p464f 1/1 Running 1 (63m ago) 80m 192.168.56.32 k8s-node2 kube-system kube-proxy-xb4h6 1/1 Running 1 (63m ago) 80m 192.168.56.31 k8s-node1 kube-system kube-scheduler-k8s-master 1/1 Running 1 (63m ago) 98m 192.168.56.30 k8s-master tigera-operator tigera-operator-cffd8458f-srgq5 0/1 ImagePullBackOff 0 89s 192.168.56.32 k8s-node2 [root@k8s-master ~]# [root@k8s-node2 ~]# docker pull quay.io/tigera/operator:v1.29.0 v1.29.0: Pulling from tigera/operator 749705320018: Pulling fs layer fc21612f0d50: Pulling fs layer e5c5babd8e74: Pulling fs layer c9aed26feef0: Waiting aa46afbc1309: Waiting b39dee2bcafd: Waiting 781629545639: Waiting error pulling image configuration: Get "https://cdn03.quay.io/sha256/34/343ea4f89a32c8f197173c5d9f1ad64eb033df452c5b89a65877d8d3cfa692b1?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAI5LUAQGPZRPNKSJA%2F20231017%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20231017T075552Z&X-Amz-Expires=600&X-Amz-SignedHeaders=host&X-Amz-Signature=52bfe5e89f7195145f8fba675b3b082f44c6f540eeecc3be6ca3fb16d2c53a8d&cf_sign=mHdRmauN8PoTOTxLhrR%2BeI6wURLJ3hQMiPz8R1%2FMM5gTdTjgtGdu8PcuMpSemMpFPu%2B%2Fl4fYpV4pnjsBI7FdJhOoiU8SZyVEpbJSmL%2FZISY880UquwT6D7cNQTw%2FvXlFw%2BKTC%2BI5BonKCj7h1zRXAehFk3F0UT8VNDRLN7AbzAsp6JN8moMDry7ATZ%2Bcfd%2FUaZrcqqQdFuyrQdyq2o4sHZVa0oj1ctVlCm8jWfuOJS7Ob2Vuo1B39WRqyqiwMjznjAZEnvoRJdXBv6vH%2BSFtUqlDSQE%2FBquSQYhmg%2FJe%2B300qus31n9gi2XJQj%2FtLmAKzPK6Vj8x0MfzvOWrbNn7lQ%3D%3D&cf_expiry=1697529952®ion=us-east-1": x509: certificate signed by unknown authority

vagrant up 오류 문의

그런데...Dashboad페이지가 안뜨네요..{ "kind": "Status", "apiVersion": "v1", "metadata": { }, "status": "Failure", "message": "services \"kubernetes-dashboard\" not found", "reason": "NotFound", "details": { "name": "kubernetes-dashboard", "kind": "services" }, "code": 404 }[root@k8s-master ~]# kubectl get pod -A NAMESPACE NAME READY STATUS RESTARTS AGE kube-system coredns-78fcd69978-d42t6 0/1 Pending 0 27m kube-system coredns-78fcd69978-h7pb5 0/1 Pending 0 27m kube-system etcd-k8s-master 1/1 Running 0 27m kube-system kube-apiserver-k8s-master 1/1 Running 0 27m kube-system kube-controller-manager-k8s-master 1/1 Running 0 27m kube-system kube-proxy-5sgbs 1/1 Running 0 27m kube-system kube-proxy-p464f 1/1 Running 0 9m34s kube-system kube-proxy-xb4h6 1/1 Running 0 9m41s kube-system kube-scheduler-k8s-master 1/1 Running 0 27m tigera-operator tigera-operator-cffd8458f-7zvq9 0/1 ErrImagePull 0 27m [root@k8s-master ~]# kubectl get pod -A NAMESPACE NAME READY STATUS RESTARTS AGE kube-system coredns-78fcd69978-d42t6 0/1 Pending 0 29m kube-system coredns-78fcd69978-h7pb5 0/1 Pending 0 29m kube-system etcd-k8s-master 1/1 Running 0 30m kube-system kube-apiserver-k8s-master 1/1 Running 0 30m kube-system kube-controller-manager-k8s-master 1/1 Running 0 30m kube-system kube-proxy-5sgbs 1/1 Running 0 29m kube-system kube-proxy-p464f 1/1 Running 0 11m kube-system kube-proxy-xb4h6 1/1 Running 0 12m kube-system kube-scheduler-k8s-master 1/1 Running 0 30m tigera-operator tigera-operator-cffd8458f-7zvq9 0/1 ImagePullBackOff 0 29m coredns가 pending상태이고, tigera-operator는 ImagePullBackOff / ErrImagePull 왔다갔다 하네요. [root@k8s-master ~]# kubectl get nodes NAME STATUS ROLES AGE VERSION k8s-master NotReady control-plane,master 32m v1.22.0 k8s-node1 NotReady 14m v1.22.0 k8s-node2 NotReady 14m v1.22.0 이건 어떻게 해결해야 할까요?