-
Notifications
You must be signed in to change notification settings - Fork 338
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
apisix-ingress-controller日志一直报错 #659
Comments
can you try to delete apisix-ingress-controller pod? (or kubectl rollout restart it) |
it seems normal,but still 404 |
can you please delete your ingress resource and re-apply it ? |
helm delete apisix -n ingress-apisix ? |
no, only need kubectl delete ingress resource |
@RunYuannn Where is the namespace of the ingress resource? |
@tokers ingress-apisix. same namespace as apisix |
@marchlhw what's your apisix-ingress version? It looks like the APISIX Ingress controller is not connected to the APISIX cluster. |
@tao12345666333 If I remember correctly, we don't merge the #774 in 1.3.0? |
@marchlhw Please try to restart APISIX Ingress controller. |
|
@marchlhw please refer to #851 (comment) I will fix the Helm chat today. |
@marchlhw @RunYuannn Do you still have problems if you use the latest version? |
This issue has not been updated for too long, and based on current testing and some feedback, the issue has been fixed. I will close it. If you still have this problem, please feel free to reply or reopen it. |
Issue description
按照文档 Install Ingress APISIX on K3S and Rancher RKE安装,但是apisix-ingress-controller pod一直刷error日志,并按照文档 Proxy the httpbin service with Ingress 配置ingress无效
apisix-ingress-controller 日志报错:
404:
yaml:
Environment
apisix-ingress-controller version --long
);kubectl version
);The text was updated successfully, but these errors were encountered: