詳細(xì)查看所有pod的運(yùn)行情況秽晚，包括IP豌熄，所在NODE等。
kubectl get pod -n ipes-nanjing -owide
進(jìn)入容器內(nèi)部
kubectl exec -it screen-web-f44d9dc4d-pqjp8 -n ipes-nanjing bash
本地映射端口
kubectl port-forward -n prj-hangzhou svc/mysql-server --address=0.0.0.0 3306:3306
kubectl get configmap??-n dmp-dev
kubectl get pods -n dmp-dev
kubectl get pvc -n dmp-dev
kubectl get deployment -n dmp-dev
kubectl get statefulset -n dmp-dev
kubectl get service -n dmp-dev
kubectl get ingress -n dmp-dev
kubectl get??deployment -n dmp-dev
kubectl get??service -n dmp-dev
kubectl edit statefulset/crawlab-master??-n dmp-dev
kubectl edit statefulset/crawlab-worker???-n dmp-dev
kubectl edit deployment/crawlab-worker???-n dmp-dev
校驗(yàn)yml文件
kubectl create -f crawlab-master-ingress.yaml??--dry-run --validate=true
kubectl edit??deploy mysql-server -n dmp-dev -oyamlv
kubectl get pods -n dmp-dev -owide
kubectl??delete deployment -n dmp-dev --all
kubectl??delete service -n dmp-dev --all
kubectl??delete pod -n dmp-dev --all
kubectl??delete statefulset -n dmp-dev --all
kubectl describe pod crawlab-master-0??-n dmp-dev
kubectl describe statefulset crawlab-master??-n dmp-dev
kubectl describe service crawlab??-n dmp-dev
kubectl describe ingress crawlab??-n dmp-dev
kubectl logs??my-crawlab-3 -n dmp-dev
kubectl -n dmp-dev??exec??-it crawlab-master-0 -- bash
kubectl -n dmp-dev??exec??-it redis-server-557db9c876-h8jvp -- bash
kubectl -n dmp-dev??exec??-it mysql-server-64cd6ccbc8-dbgrc??-- bash
kubectl apply -f mysql.yml -n dmp-dev
kubectl apply -f mongo.yml -n dmp-dev
kubectl apply -f redis-new.yml -n dmp-dev
kubectl apply -f crawlab-master.yaml??-n dmp-dev
kubectl apply -f crawlab-worker.yaml??-n dmp-dev
kubectl apply -f crawlab-master-ingress.yaml??-n dmp-dev
kubectl create configmap mongo-server-initialization??--from-file=cm/mongo-server-initialization/??-n dmp-dev
kubectl create configmap redis-server-health??--from-file=cm/redis-server-health/??-n dmp-dev
kubectl run my-crawlab??--image=tikazyq/crawlab:latest??--port=8080??--limits=cpu=200m,memory=512Mi -n dmp-dev
kubectl run my-crawlab-3??--image=tikazyq/crawlab:latest --port=8080??--limits=cpu=200m,memory=512Mi -n dmp-dev
#獲得當(dāng)前所有的命名空間
//查看命名空間
kubectl get ns
//查看節(jié)點(diǎn)
kubectl get node
#啟動docker.service服務(wù)
systemctl start? docker.service
#查看啟動結(jié)果
systemctl status docker.service
#設(shè)置為開機(jī)啟動
systemctl enable? docker.service
#K8S 服務(wù)重啟
systemctl? ?status? ??kubelet
#更新參數(shù)
systemctl daemon-reload
systemctl? ?restart? ?kubelet
systemctl start? kubelet
#設(shè)置為開機(jī)啟動
systemctl enable? kubelet
https://blog.csdn.net/yujia_666/article/details/114118291
強(qiáng)制刪除POD
kubectl delete pod xxx -n xxx --force --grace-period=0
kubectl patch pod xxx -n xxx -p '{"metadata":{"finalizers":null}}'
1. pod刪除
每當(dāng)刪除namespace或pod 等一些Kubernetes資源時(shí)，有時(shí)資源狀態(tài)會卡在terminating演侯，很長時(shí)間無法刪除，甚至有時(shí)增加--force flag(強(qiáng)制刪除)之后還是無法正常刪除背亥。這時(shí)就需要edit該資源秒际，將字段finalizers設(shè)置為null，之后Kubernetes資源就正常刪除了狡汉。
當(dāng)刪除pod時(shí)有時(shí)會卡住娄徊，pod狀態(tài)變?yōu)閠erminating，無法刪除pod
（1)強(qiáng)制刪除
kubectl delete pod xxx -n xxx --force --grace-period=0
（2)如果強(qiáng)制刪除還不行盾戴，設(shè)置finalizers為空
（如果一個(gè)容器已經(jīng)在運(yùn)行寄锐，這時(shí)需要對一些容器屬性進(jìn)行修改，又不想刪除容器，或不方便通過replace的方式進(jìn)行更新锐峭。kubernetes還提供了一種在容器運(yùn)行時(shí)中鼠，直接對容器進(jìn)行修改的方式，就是patch命令沿癞。）
kubectl patch pod xxx -n xxx -p '{"metadata":{"finalizers":null}}'
這樣pod就可以刪除了援雇。
-----------------------------NodePort-------------------------------
