clean up kubernetes setup - jamongx/twitter-clone GitHub Wiki
-
7 instances after creating a cluster
-
Check deployment to delete
[root@k8s-server ~]# kubectl get all
NAME READY STATUS RESTARTS AGE
pod/jamongx-user-service-544d74d6fb-89mj8 1/1 Running 0 20h
pod/jamongx-user-service-544d74d6fb-g6gr2 1/1 Running 0 20h
pod/jamongx-user-service-544d74d6fb-h6mkj 1/1 Running 0 20h
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/jamongx-service LoadBalancer xxx.100.xxx.37 xxx.us-east-2.elb.amazonaws.com xxxx:xxxx/TCP 4d21h
service/kubernetes ClusterIP xxx.100.xxx.1 <none> xxx/TCP 5d11h
NAME READY UP-TO-DATE AVAILABLE AGE
deployment.apps/jamongx-user-service 3/3 3 3 4d21h
NAME DESIRED CURRENT READY AGE
replicaset.apps/jamongx-user-service-544d74d6fb 3 3 3 3d12h
replicaset.apps/jamongx-user-service-78ddf66b46 0 0 0 4d21h
replicaset.apps/jamongx-user-service-84fdbbf8d 0 0 0 4d12h
replicaset.apps/jamongx-user-service-855c78db76 0 0 0 4d21h
- Delete deployment
[root@k8s-server ~]# kubectl delete deployment.apps/jamongx-user-service
deployment.apps "jamongx-user-service" deleted
[root@k8s-server ~]# kubectl get all
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/jamongx-service LoadBalancer xxx.100.xxx.37 xxx.us-east-2.elb.amazonaws.com xxxx:xxxx/TCP 4d21h
service/kubernetes ClusterIP xxx.100.xxx.1 <none>
- Delete Service
[root@k8s-server ~]# kubectl delete service/jamongx-service
service "jamongx-service" deleted
[root@k8s-server ~]# kubectl get all
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
service/kubernetes ClusterIP xxx.100.xxx.1 <none> 443/TCP 5d11h
- Delete Cluster
[root@k8s-server ~]# kubectl get nodes
NAME STATUS ROLES AGE VERSION
ip-xxx-168-xxx-180.us-east-2.compute.internal Ready <none> 20h v1.25.13-eks-43840fb
ip-xxx-168-xxx-237.us-east-2.compute.internal Ready <none> 20h v1.25.13-eks-43840fb
[root@k8s-server ~]# eksctl delete cluster jamongx --region us-east-2
- 2 instances after deleting the cluster
