-
Notifications
You must be signed in to change notification settings - Fork 367
Description
Description
Issue: Apisix ingress controller pod is init state only. Below the ref details .
Referred URL: https://apisix.apache.org/docs/helm-chart/apisix-ingress-controller/
~/helm list -n ingress-apisix
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
apisix-ingress-controller ingress-apisix 1 2024-02-07 12:17:06.652685738 +0000 UTC deployed apisix-ingress-controller-0.14.0 1.8.0
apisix-test ingress-apisix 1 2024-02-07 12:20:22.903447122 +0000 UTC deployed apisix-2.6.0 3.8.0
kubectl get pods -n ingress-apisix
NAME READY STATUS RESTARTS AGE
apisix-ingress-controller-fbf694678-lsh6h 0/1 Init:0/1 0 5m22s
Pod Describe:
Events:
Type Reason Age From Message
Normal Scheduled 8m39s default-scheduler Successfully assigned ingress-apisix/apisix-ingress-controller-fbf694678-lsh6h to ip-10-5-3-140.us-west-2.compute.internal
Normal Pulling 8m39s kubelet Pulling image "busybox:1.28"
Normal Pulled 8m37s kubelet Successfully pulled image "busybox:1.28" in 1.48804606s
Normal Created 8m37s kubelet Created container wait-apisix-admin
Normal Started 8m37s kubelet Started container wait-apisix-admin
Environment
AWS EKS Cluster
- APISIX version 3.8.0:
- Operating system (run
uname -a): AWS EKS Worker ( 5.10.82-83.359.amzn2.x86_64) - Plugin runner version, for issues related to plugin runners: