GhangZh opened a new issue, #974:
URL: https://github.com/apache/apisix-ingress-controller/issues/974
### Issue description
After upgrading apisix 1.13and apisix-ingress-controller 1.4 through helm,
ingress-controller will automatically synchronize the current ar file to apisix
and add the field plugin_config_id
```bash
apiVersion: apisix.apache.org/v2beta3
kind: ApisixRoute
metadata:
name: test
namespace: test
spec:
http:
- backends:
- serviceName: test
servicePort: 80
match:
hosts:
- apisix-test.com
paths:
- /cluster/idc*
name: test
plugins:
- name: proxy-rewrite
enable: true
config:
regex_uri: ["^/cluster/idc(.*)", "/$1"]
```
apisix-ingress-controller log
curl http://127.0.0.1:9180/apisix/admin/plugin_configs -H 'X-API-KEY:
edd1c9f034335f136f87ad84b625c8f1'
### Environment
- your apisix-ingress-controller version (output of
apisix-ingress-controller version --long):
- your Kubernetes cluster version (output of kubectl version):
- if you run apisix-ingress-controller in Bare-metal environment, also show
your OS version (uname -a):
### Minimal test code / Steps to reproduce
kubectl apply -f test.yaml
kubectl exec -it apisix-544b6cbf74-npr5z -n ingress-apisix bash
curl http://127.0.0.1:9180/apisix/admin/plugin_configs -H 'X-API-KEY:
edd1c9f034335f136f87ad84b625c8f1'
### Actual result
No plugin_config_id
### Error log
```bash
warn ingress/compare.go:186pluginConfig: 2930e8f3 in APISIX but do
not in declare yaml
2022-04-20T16:13:34+08:00
warn ingress/compare.go:186pluginConfig: 2930e8f3 in APISIX but do
not in declare yaml
```
### Expected result
_No response_
--
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]
