xianshun163 commented on issue #860:
URL:
https://github.com/apache/apisix-ingress-controller/issues/860#issuecomment-1035955345
hi, @tao12345666333
I have deploy the ingress version 1.3.0 by the follow step：
1、kubectl apply -k samples/deploy/crd -n ingress-apisix
2、kubectl apply -k samples/deploy/rbac -n ingress-apisix
3、kubectl apply -k samples/deploy/admission -n ingress-apisix
4、kubectl apply -k samples/deploy/configmap -n ingress-apisix
5、kubectl apply -k samples/deploy/deployment -n ingress-apisix
It work ok, I can create some apisixroute for the apisix.
but, when I change the images version to 1.4.0 , the po can not run, it
is a err like this, do you know how to upgrade to 1.4.0?
:
`bash
I0211 15:46:23.897763 1 leaderelection.go:248] attempting to acquire
leader lease ingress-apisix/ingress-apisix-leader...
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x48 pc=0xde92db]
goroutine 52 [running]:
github.com/apache/apisix-ingress-controller/pkg/apisix.(*cluster).getList(0xc0000d06c0,
0x1fd9c28, 0xc0000c0018, 0xc0002da000, 0x33, 0x1d3fef7, 0x6, 0x0, 0x0, 0x0,
...)
/build/controller/pkg/apisix/cluster.go:739 +0x19b
github.com/apache/apisix-ingress-controller/pkg/apisix.(*pluginClient).List(0xc00041fd40,
0x1fd9c28, 0xc0000c0018, 0x0, 0x0, 0x0, 0x1, 0x0)
/build/controller/pkg/apisix/plugin.go:44 +0x3b9
github.com/apache/apisix-ingress-controller/pkg/apisix.(*cluster).syncSchemaOnce(0xc0000d06c0,
0x1fd9c28, 0xc0000c0018, 0x0, 0x0)
/build/controller/pkg/apisix/cluster.go:388 +0x74f
github.com/apache/apisix-ingress-controller/pkg/apisix.(*cluster).syncSchema(0xc0000d06c0,
0x1fd9c28, 0xc0000c0018, 0x13a52453c000)
/build/controller/pkg/apisix/cluster.go:352 +0xa5
created by github.com/apache/apisix-ingress-controller/pkg/apisix.newCluster
/build/controller/pkg/apisix/cluster.go:152 +0x8f4
`
--
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]
