전체 글139 [cka] TroubleShooting - Worker Node Failure 1. Fix the broken cluster controlplane ~ ➜ k get nodesNAME STATUS ROLES AGE VERSIONcontrolplane Ready control-plane 11m v1.30.0node01 NotReady 11m v1.30.0controlplane ~ ➜ k get pods -ANAMESPACE NAME READY STATUS RESTARTS AGEkube-flannel kube-flannel-ds-c8pzs 1/1 Runni.. 2024. 8. 25. [cka] TroubleShooting - Control Plane Failure 1.The cluster is broken. We tried deploying an application but it's not working. Troubleshoot and fix the issue.Start looking at the deployments. ontrolplane ~ ➜ k get all -ANAMESPACE NAME READY STATUS RESTARTS AGEdefault pod/app-5f58858856-hdm6s 0/1 Pending 0 45skube-flannel pod/.. 2024. 8. 25. [cka] TroubleShooting - Application Failure 1. Troubleshooting Test 1: A simple 2 tier application is deployed in the alpha namespace. It must display a green web page on success. Click on the App tab at the top of your terminal to view your application. It is currently failed. Troubleshoot and fix the issue. Stick to the given architecture. Use the same names and port numbers as given in the below architecture diagram. Feel free to edit,.. 2024. 8. 25. [cka] Cluster Installation using Kubeadm 1. Install the kubeadm and kubelet packages on the controlplane and node01 nodes.Use the exact version of 1.30.0-1.1 for both. 1-1. set net.bridge.bridge-nf-call-iptables to 1cat 1-2. install container runtime.해당 연구실실습에서는 설치되어 있다. (The container runtime has already been installed on both nodes, so you may skip this step.) 1-3. Install kubeadm, kubectl and kubelet on all nodessudo apt-get update.. 2024. 8. 25. [cka] Ingress Networking - 2 1. We have deployed two applications. Explore the setup. Note: They are in a different namespace. controlplane ~ ➜ k get all -ANAMESPACE NAME READY STATUS RESTARTS AGEapp-space pod/default-backend-78f6fb8b4-sxpj7 1/1 Running 0 54sapp-space pod/webapp-video-74bdc86cb8-xms4v 1/1 Running 0 54s.. 2024. 8. 13. 이전 1 2 3 4 5 6 7 ··· 28 다음 반응형
