help request: Apisix 3.8.0 version - ingress controller deployment issue

[Gokulk7]

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:

[github-actions[bot]]

This issue has been marked as stale due to 90 days of inactivity. It will be closed in 30 days if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the [email protected] list. Thank you for your contributions.

[kayx23]

Hi there, I have recently installed the latest APISIX ingress controller with helm and have no such issue.

The installation (with kind) is now documented here end-to-end: https://docs.api7.ai/apisix/getting-started/ (under Kubernetes tab)

Closing this issue now. If you still run into the same error somehow, feel free to reopen.