stubbornTanzhe commented on PR #1633:
URL:
https://github.com/apache/apisix-ingress-controller/pull/1633#issuecomment-1410027965
```
[CMCC.DESKTOP-FL84U1K] ➤ kubectl get po -n apisix -owide
NAME READY STATUS RESTARTS
AGE IP NODE NOMINATED NODE READINESS GATES
apisix-58cb57b4b4-ztpn7 1/1 Running 0
42m 10.1.2.140 docker-desktop <none> <none>
apisix-ingress-controller-77899f968b-ksvlq 1/1 Running 0
25m 10.1.2.141 docker-desktop <none> <none>
etcd-0 1/1 Running 2 (110m ago)
5h58m 10.1.2.135 docker-desktop <none> <none>
[CMCC.DESKTOP-FL84U1K] ➤ kubectl describe pod
apisix-ingress-controller-77899f968b-ksvlq -n apisix
Name: apisix-ingress-controller-77899f968b-ksvlq
Namespace: apisix
Priority: 0
Service Account: apisix-ingress-controller
Node: docker-desktop/192.168.65.4
Start Time: Tue, 31 Jan 2023 16:58:16 +0800
Labels: app.kubernetes.io/name=ingress-controller
pod-template-hash=77899f968b
Annotations: <none>
Status: Running
IP: 10.1.2.141
IPs:
IP: 10.1.2.141
Controlled By: ReplicaSet/apisix-ingress-controller-77899f968b
Init Containers:
wait-apisix-admin:
Container ID:
docker://5a7d559abf381d69f05e1a0410b135a292d0ff7c282d729816ecd01dc1b4342f
Image: busybox:1.28
Image ID:
docker-pullable://busybox@sha256:141c253bc4c3fd0a201d32dc1f493bcf3fff003b6df416dea4f41046e0f37d47
Port: <none>
Host Port: <none>
Command:
sh
-c
until nc -z apisix-admin.apisix.svc.cluster.local 9180 ; do echo
waiting for apisix-admin; sleep 2; done;
State: Terminated
Reason: Completed
Exit Code: 0
Started: Tue, 31 Jan 2023 16:58:17 +0800
Finished: Tue, 31 Jan 2023 16:58:17 +0800
Ready: True
Restart Count: 0
Environment: <none>
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from
kube-api-access-q9bd7 (ro)
Containers:
ingress-controller:
Container ID:
docker://9fa1ba60ce20d22763e79c9dc3fc4cfc42eaae30b196edcb639ef626937c9193
Image: apache/apisix-ingress-controller:1.4.0
Image ID:
docker-pullable://apache/apisix-ingress-controller@sha256:eb8c38ab72a96b8953f135b91208fced232d335a63d031e6c468bade50d73c93
Port: 8080/TCP
Host Port: 0/TCP
Command:
/ingress-apisix/apisix-ingress-controller
ingress
--config-path
/ingress-apisix/conf/config.yaml
State: Running
Started: Tue, 31 Jan 2023 16:58:47 +0800
Ready: True
Restart Count: 0
Liveness: http-get http://:8080/healthz delay=0s timeout=1s
period=10s #success=1 #failure=3
Readiness: http-get http://:8080/healthz delay=0s timeout=1s
period=10s #success=1 #failure=3
Environment: <none>
Mounts:
/ingress-apisix/conf from configuration (rw)
/var/run/secrets/kubernetes.io/serviceaccount from
kube-api-access-q9bd7 (ro)
Conditions:
Type Status
Initialized True
Ready True
ContainersReady True
PodScheduled True
Volumes:
configuration:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: apisix-configmap
Optional: false
kube-api-access-q9bd7:
Type: Projected (a volume that contains injected data
from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional: <nil>
DownwardAPI: true
QoS Class: BestEffort
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 Scheduled 26m default-scheduler Successfully assigned
apisix/apisix-ingress-controller-77899f968b-ksvlq to docker-desktop
Normal Pulled 26m kubelet Container image "busybox:1.28"
already present on machine
Normal Created 26m kubelet Created container
wait-apisix-admin
Normal Started 26m kubelet Started container
wait-apisix-admin
Normal Pulling 25m kubelet Pulling image
"apache/apisix-ingress-controller:1.4.0"
Normal Pulled 25m kubelet Successfully pulled image
"apache/apisix-ingress-controller:1.4.0" in 28.5811805s
Normal Created 25m kubelet Created container
ingress-controller
Normal Started 25m kubelet Started container
ingress-controller
[CMCC.DESKTOP-FL84U1K] ➤ kubectl describe pod apisix-58cb57b4b4-ztpn7 -n
apisix
Name: apisix-58cb57b4b4-ztpn7
Namespace: apisix
Priority: 0
Service Account: default
Node: docker-desktop/192.168.65.4
Start Time: Tue, 31 Jan 2023 16:40:52 +0800
Labels: app.kubernetes.io/name=apisix
pod-template-hash=58cb57b4b4
Annotations: <none>
Status: Running
IP: 10.1.2.140
IPs:
IP: 10.1.2.140
Controlled By: ReplicaSet/apisix-58cb57b4b4
Containers:
apisix:
Container ID:
docker://803de66bf544b16cecf8f9b16cbe903978bf391b30f9b601ae9edb176e0d10f6
Image: apache/apisix:2.15.0-alpine
Image ID:
docker-pullable://artifactory.dep.devops.cmit.cloud:20101/panji_middleware/apisix@sha256:c56359999040af69a34b2d91f24c94e513f8a0eb06eaa
6d3063fb0e9bc9b0678
Ports: 9080/TCP, 9443/TCP, 9180/TCP
Host Ports: 0/TCP, 0/TCP, 0/TCP
State: Running
Started: Tue, 31 Jan 2023 16:40:55 +0800
Ready: True
Restart Count: 0
Readiness: tcp-socket :9080 delay=10s timeout=1s period=10s
#success=1 #failure=6
Environment: <none>
Mounts:
/usr/local/apisix/conf/config.yaml from apisix-config
(rw,path="config.yaml")
/var/run/secrets/kubernetes.io/serviceaccount from
kube-api-access-6cqfp (ro)
Conditions:
Type Status
Initialized True
Ready True
ContainersReady True
PodScheduled True
Volumes:
apisix-config:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: apisix-conf
Optional: false
kube-api-access-6cqfp:
Type: Projected (a volume that contains injected data
from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional: <nil>
DownwardAPI: true
QoS Class: BestEffort
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 Scheduled 44m default-scheduler Successfully assigned
apisix/apisix-58cb57b4b4-ztpn7 to docker-desktop
Normal Pulled 44m kubelet Container image
"apache/apisix:2.15.0-alpine" already present on machine
Normal Created 44m kubelet Created container apisix
Normal Started 44m kubelet Started container apisix
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
