【BUG】: unknown plugin [coraza-filter]

[DokiDoki1103]

Issue description

• I successfully modified the configuration file

• There is also a wasm plugin in the container

I have also restarted the container multiple times, but if I want to use the WAF plugin, I will prompt that the plugin is not found

The configuration file inside the container has also taken effect。

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):

apache/apisix-ingress-controller:1.7.1
apache/apisix:3.6.0-centos

[DokiDoki1103]

I have read this document and successfully deployed it

https://apisix.incubator.apache.org/zh/blog/2023/10/18/ingress-apisix/

I noticed that the version provided on Git is not the latest version,

https://github.com/apache/apisix-ingress-controller/blob/master/samples/deploy/composite.yaml#L455

But I have changed it to the latest version apisix:3.6.0-centos

[DokiDoki1103]

I configure it declaratively through CRD and it doesn't work either

[DokiDoki1103]

cc @Revolyssup

This may also be a bug ，The same API can be configured, but the ingress controller cannot

[github-actions[bot]]

This issue has been marked as stale due to 90 days of inactivity. It will be closed in 30 days if no further activity occurs. If this issue is still relevant, please simply write any comment. Even if closed, you can still revive the issue at any time or discuss it on the [email protected] list. Thank you for your contributions.

[github-actions[bot]]

This issue has been closed due to lack of activity. If you think that is incorrect, or the issue requires additional review, you can revive the issue at any time.