apisix-ingress-controller
apisix-ingress-controller copied to clipboard
bug: ApisixIngress ApisixIngress synced failed, with error: upstream doesn't exist.
Current Behavior
我们有好几个集群在使用apisix ingress。近期新部署了一个apisix ingress,版本最新的:apisix:3.12,apisix-ingress:1.8.4。在创建apisixupstream 时候查看apixupstream 提示同步失败:ApisixIngress synced failed, with error: upstream doesn't exist. It will be created after ApisixRoute is created referencing it. 但是访问对应的地址是没问题的。我们其他环境没有这个报错,我把版本回退到如下版本(apisix-ingress: 1.6.1, apisix:3.2.1)后正常了,如图所示更新后显示状态成功。
Expected Behavior
No response
Error Logs
No response
Steps to Reproduce
1、通过helm chart安装ingress 1、依次创建apisixupstream apisixroute
Environment
- APISIX Ingress controller version (run
apisix-ingress-controller version --long) ingress controller: 3.8.4 - Kubernetes cluster version (run
kubectl version) 1.32 - OS version if running APISIX Ingress controller in a bare-metal environment (run
uname -a) 阿里云linux 3
我测试了下各个版本: apisix ingress controller:3.7.1 3.8.4 都有这个问题。apisix 最新几个版本切换都没有问题不会影响。目前用的apisix:3.12.0, apisix-ingress-controller: 3.6.1。感觉controller有问题。如图是不同controller版本后apisixupstream切换的describe 状态。
如图是对应的yaml写法和对应svc。
确实是有这个问题,ingress 1.6.X 的是正常的,怀疑是版本迭代中引入了BUG,看官方一直没修复。准备自己研究一下代码了
发现降级到 1.6.1 版本就正常了,可以试试
We are building a new IC which will resolve this issue.
We are building a new IC which will resolve this issue.
if there update with this bug?
We are building a new IC which will resolve this issue.
if there update with this bug?
Hi @yangvipguang @VanLiuZhi @shoulda @FlyTOmeLight, the latest v2.0.0-rc3 version has been released, which includes the fix for this issue and a series of architectural adjustments and optimizations. Please use the latest version to try it out.
If there is still a problem, please open it again.