单节点安装kubesphere后，default-http-backend起不来
[root@c2 kubesphere]# kubectl get pod -A
NAMESPACE NAME READY STATUS RESTARTS AGE
his his-mysql-0 1/1 Running 0 23m
kube-system calico-kube-controllers-8545b68dd4-zrx6v 1/1 Running 0 2d11h
kube-system calico-node-89p2l 1/1 Running 0 2d11h
kube-system coredns-7f87749d6c-qqblg 1/1 Running 0 2d11h
kube-system coredns-7f87749d6c-xj6fc 1/1 Running 0 2d11h
kube-system kube-apiserver-c2 1/1 Running 0 2d11h
kube-system kube-controller-manager-c2 1/1 Running 0 2d11h
kube-system kube-proxy-sj4bp 1/1 Running 0 2d11h
kube-system kube-scheduler-c2 1/1 Running 0 2d11h
kube-system nodelocaldns-nbv56 1/1 Running 0 2d11h
kube-system openebs-localpv-provisioner-5cddd6cbfc-h2b4f 1/1 Running 0 2d11h
kube-system snapshot-controller-0 1/1 Running 0 2d11h
kubesphere-controls-system default-http-backend-5d7c68c698-lhm45 0/1 ContainerCreating 0 42h
kubesphere-controls-system kubectl-admin-68dc989bf8-q97pc 1/1 Running 0 2d11h
kubesphere-monitoring-system alertmanager-main-0 2/2 Running 0 2d11h
kubesphere-monitoring-system kube-state-metrics-577b8b4cf-cn8sd 3/3 Running 0 2d11h
kubesphere-monitoring-system node-exporter-hz7l4 2/2 Running 0 2d11h
kubesphere-monitoring-system notification-manager-deployment-97dfccc89-z859d 1/1 Running 0 2d11h
kubesphere-monitoring-system notification-manager-operator-59cbfc566b-c2gkr 2/2 Running 0 2d11h
kubesphere-monitoring-system prometheus-k8s-0 3/3 Running 2 2d11h
kubesphere-monitoring-system prometheus-operator-8f97cb8c6-lj7cg 2/2 Running 0 2d11h
kubesphere-system ks-apiserver-54d446b65c-x6thl 1/1 Running 0 2d11h
kubesphere-system ks-console-58b965dbf5-8t64c 1/1 Running 0 2d11h
kubesphere-system ks-controller-manager-76655c79bd-mrhtz 1/1 Running 0 2d11h
kubesphere-system ks-installer-769994b6ff-gq6hz 1/1 Running 0 2d11h
mysql mysql-0 1/1 Running 0 37h
[root@c2 kubesphere]# kubectl describe pod default-http-backend-5d7c68c698-lhm45 -n kubesphere-controls-system
Name: default-http-backend-5d7c68c698-lhm45
Namespace: kubesphere-controls-system
Priority: 0
Node: c2/10.240.208.172
Start Time: Sat, 16 Oct 2021 17:29:29 +0800
Labels: app=kubesphere
component=kubesphere-router
pod-template-hash=5d7c68c698
Annotations: <none>
Status: Pending
IP:
IPs: <none>
Controlled By: ReplicaSet/default-http-backend-5d7c68c698
Containers:
default-http-backend:
Container ID:
Image: registry.cn-beijing.aliyuncs.com/kubesphereio/defaultbackend-amd64:1.4
Image ID:
Port: 8080/TCP
Host Port: 0/TCP
State: Waiting
Reason: ContainerCreating
Ready: False
Restart Count: 0
Limits:
cpu: 10m
memory: 20Mi
Requests:
cpu: 10m
memory: 20Mi
Liveness: http-get http://:8080/healthz delay=30s timeout=5s period=10s #success=1 #failure=3
Environment: <none>
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from default-token-hf8hm (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
default-token-hf8hm:
Type: Secret (a volume populated by a Secret)
SecretName: default-token-hf8hm
Optional: false
QoS Class: Guaranteed
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
Normal SandboxChanged 14m (x859 over 42h) kubelet Pod sandbox changed, it will be killed and re-created.
Warning FailedCreatePodSandBox 3m56s (x863 over 42h) kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to start sandbox container for pod “default-http-backend-5d7c68c698-lhm45”: operation timeout: context deadline exceeded
[root@c2 kubesphere]#
[root@c2 kubesphere]# kubectl logs default-http-backend-5d7c68c698-lhm45 -n kubesphere-controls-system
Error from server (BadRequest): container “default-http-backend” in pod “default-http-backend-5d7c68c698-lhm45” is waiting to start: ContainerCreating
[root@c2 kubesphere]#