在执行kubectl apply -f deploy.yaml 命令时出现以下错误
出现原因:
执行了kubectl delete -f deploy.yaml 命令,删除了命名空间ingress-nginx,导致后续操作无法执行
解决方法:
#查看命名空间,ingress-nginx命名空间不存在
[root@kuber-master cloud]# kubectl get ns
NAME STATUS AGE
default Active 7d5h
kube-node-lease Active 7d5h
kube-public Active 7d5h
kube-system Active 7d5h
kuboard Active 4d5h
webserver Active 6d4h
#创建命名空间
[root@kuber-master cloud]# kubectl create namespace ingress-nginx
namespace/ingress-nginx created
#重新执行apply命令
[root@kuber-master cloud]# kubectl apply -f deploy.yaml
Warning: resource namespaces/ingress-nginx is missing the kubectl.kubernetes.io/last-applied-configuration annotation which is required by kubectl apply. kubectl apply should only be used on resources created declaratively by either kubectl create --save-config or kubectl apply. The missing annotation will be patched automatically.
namespace/ingress-nginx configured
serviceaccount/ingress-nginx created
serviceaccount/ingress-nginx-admission created
role.rbac.authorization.k8s.io/ingress-nginx created
role.rbac.authorization.k8s.io/ingress-nginx-admission created
clusterrole.rbac.authorization.k8s.io/ingress-nginx unchanged
clusterrole.rbac.authorization.k8s.io/ingress-nginx-admission unchanged
rolebinding.rbac.authorization.k8s.io/ingress-nginx created
rolebinding.rbac.authorization.k8s.io/ingress-nginx-admission created
clusterrolebinding.rbac.authorization.k8s.io/ingress-nginx unchanged
clusterrolebinding.rbac.authorization.k8s.io/ingress-nginx-admission unchanged
configmap/ingress-nginx-controller created
service/ingress-nginx-controller created
service/ingress-nginx-controller-admission created
daemonset.apps/ingress-nginx-controller created
job.batch/ingress-nginx-admission-create created
job.batch/ingress-nginx-admission-patch created
ingressclass.networking.k8s.io/nginx unchanged
validatingwebhookconfiguration.admissionregistration.k8s.io/ingress-nginx-admission configured
#查看一下
[root@kuber-master cloud]# kubectl get pod -A
NAMESPACE NAME READY STATUS RESTARTS AGE
default apache-dep-test-844d66746f-8knln 1/1 Running 0 31m
default apache-dep-test-844d66746f-dc248 1/1 Running 0 31m
default apache-dep-test-844d66746f-nxbpm 1/1 Running 0 31m
default apache-dep-test-844d66746f-xcdbw 1/1 Running 0 31m
default my-mysql 1/1 Running 3 (3h28m ago) 4d5h
default mysa-pod 1/1 Running 2 (3h28m ago) 3d5h
default nginx-dep-test-684c9b848b-729tn 1/1 Running 0 97m
default nginx-dep-test-684c9b848b-twxz2 1/1 Running 0 96m
default test-webapp 1/1 Running 3 (3h28m ago) 4d3h
default website 2/2 Running 8 (3h28m ago) 5d5h
ingress-nginx ingress-nginx-admission-create--1-tldc8 0/1 ContainerCreating 0 8s
ingress-nginx ingress-nginx-admission-patch--1-zdqc9 0/1 ContainerCreating 0 7s
ingress-nginx ingress-nginx-controller-bnhb9 0/1 ContainerCreating 0 8s
ingress-nginx ingress-nginx-controller-vp4fh 0/1 ContainerCreating 0 8s
kube-system calico-kube-controllers-7c87c5f9b8-bpwxd 1/1 Running 8 (3h28m ago) 7d5h
kube-system calico-node-bp29l 1/1 Running 7 (3h28m ago) 7d5h
kube-system calico-node-qmjbf 1/1 Running 7 (3h28m ago) 7d5h
kube-system calico-node-t2f5n 1/1 Running 8 (3h28m ago) 7d5h
kube-system coredns-78fcd69978-pknzj 1/1 Running 8 (3h28m ago) 7d5h
kube-system coredns-78fcd69978-xlwhg 1/1 Running 8 (3h28m ago) 7d5h
kube-system etcd-kuber-master 1/1 Running 8 (3h28m ago) 7d5h
kube-system kube-apiserver-kuber-master 1/1 Running 8 (3h28m ago) 7d5h
kube-system kube-controller-manager-kuber-master 1/1 Running 8 (3h28m ago) 7d5h
kube-system kube-proxy-28g9l 1/1 Running 0 72m
kube-system kube-proxy-cqmt8 1/1 Running 0 72m
kube-system kube-proxy-zhtz2 1/1 Running 0 72m
kube-system kube-scheduler-kuber-master 1/1 Running 8 (3h28m ago) 7d5h
kuboard kuboard-agent-2-6dd49dc5f4-t2x7n 1/1 Running 3 (3h28m ago) 4d5h
kuboard kuboard-agent-799c5d8848-bwm97 1/1 Running 3 (3h28m ago) 4d5h
kuboard kuboard-etcd-cp8kp 1/1 Running 3 (3h28m ago) 4d5h
kuboard kuboard-v3-5fc46b5557-jpkdk 1/1 Running 3 (3h28m ago) 4d5h
webserver database 1/1 Running 5 (3h28m ago) 6d4h