jjdiazgarcia commented on issue #2046:
URL:
https://github.com/apache/apisix-ingress-controller/issues/2046#issuecomment-1823913605
We are facing exactly the same issue. After defining a plugin,
apisix-ingress-controller is complaining about it
```
apiVersion: apisix.apache.org/v2
kind: ApisixPluginConfig
metadata:
annotations:
kubectl.kubernetes.io/last-applied-configuration: |
{"apiVersion":"apisix.apache.org/v2","kind":"ApisixPluginConfig","metadata":{"annotations":{},"name":"proxy-rewrite-jero-pluginconfig-test","namespace":"jero-test"},"spec":{"plugins":[{"config":{"host":"devops-pluginconfig-test.jero-test.svc.cluster.local"},"enable":true,"name":"proxy-rewrite"}]}}
creationTimestamp: "2023-11-17T13:16:31Z"
generation: 3
name: proxy-rewrite-jero-pluginconfig-test
namespace: jero-test
resourceVersion: "696627044"
uid: a94e15f4-b53c-48f5-8031-40de2671099a
spec:
plugins:
- config:
host: devops-pluginconfig-test.jero-test.svc.cluster.local
enable: true
name: proxy-rewrite
status:
conditions:
- message: Sync Successfully
observedGeneration: 3
reason: ResourcesSynced
status: "True"
type: ResourcesAvailable
```
And error log from apisix-ingress-controller
```
2023-11-23T15:23:58+08:00 error apisix/pluginconfig.go:163 failed
to create pluginConfig: unexpected status code 400; error message:
{"error_msg":"invalid configuration: additional properties forbidden, found
name"}
2023-11-23T15:23:58+08:00 warn apisix/apisix_plugin_config.go:261
sync ApisixPluginConfig failed, will retry {"object":
{"Type":1,"Object":{"Key":"jero-test/proxy-rewrite-jero-pluginconfig-test","OldObject":null,"GroupVersion":"apisix.apache.org/v2"},"OldObject":null,"Tombstone":null},
"error": "1 error occurred:\n\t* unexpected status code 400; error message:
{\"error_msg\":\"invalid configuration: additional properties forbidden, found
name\"}\n\n\n"}
```
apisix version is 3.6.0
apisix-ingress-controller version is 1.6.0
--
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]
