m4dm4rtig4n opened a new issue, #873:
URL: https://github.com/apache/apisix-helm-chart/issues/873
After upgrading to ingress-controller v2, annotations that previously
enabled specific plugins or settings (e.g.
k8s.apisix.apache.org/plugin-config-name) are no longer interpreted.
The same manifests worked correctly in v1.
**Steps to Reproduce**
1. Deploy an Ingress with an annotation:
```
metadata:
annotations:
k8s.apisix.apache.org/plugin-config-name: my-plugin
```
2. Check with kubectl describe ingress … that the annotation is present.
3. Observe that the plugin is not attached to the APISIX route.
**Expected Behavior**
The ingress-controller should create the corresponding ApisixPluginConfig
resource and attach it to the route, as in v1.
**Current Behavior**
No blocking error is logged, but the plugin is not applied.
Environment
* Helm Chart: apisix/apisix v2.11.6
* App version (APISIX): 3.13
* Kubernetes: v1.32.6+k3s1
**Additional Context**
The ingress-controller logs show no error, but the “plugin” section in the
APISIX dashboard remains empty.
--
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]
