bug: ingress-controller v2: annotations no longer seem to be supported

[m4dm4rtig4n]

Current Behavior

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.

Expected Behavior

The ingress-controller should create the corresponding ApisixPluginConfig resource and attach it to the route, as in v1.

Error Logs

No blocking error is logged, but the plugin is not applied.

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.

Environment

• Helm Chart: apisix/apisix v2.11.6
• App version (APISIX): 3.13
• Kubernetes: v1.32.6+k3s1

[bzp2010]

As of now (September 15), this is expected since we haven’t added that support yet.
We’ve mainly been focusing on first-class Gateway API support (it’s not fully there yet, but we’re making progress). On top of that, we’re also working on bringing Apisix CRD support back to the level it had in 1.x.

Right now, Ingress only has basic support, and that doesn’t include annotations that used to be supported. That’s been a lower priority for my team. Still, I do expect we’ll get to it eventually—at least restoring the annotations that were already available in 1.x. That way migration will be easier and backward compatibility is covered.

I can’t give a timeline, since the team is busy with higher-priority improvements, but it’s quite possible this will land in one of the upcoming releases.

As for Ingress annotations in general, we’re probably not going to actively expand on that standard. Annotations just don’t have the semantics to fully represent APISIX core and plugin configurations. If all we can do is put together a partial or compromise-based solution, it may not be worth the effort. This isn’t a final call yet, but it’s where our thinking is right now.

---

AIC 2.0 is a complete rewrite because the old code was pretty much rotten. Therefore, if we need certain functionality, we need to implement it from scratch.

Fortunately, since we now have a better foundation, we may be able to implement equivalent functionality with less work and provide certain features (stateless deployment) that were difficult to support in the original architecture. It is almost complete now, but it does have some side scenarios that are not fully implemented yet.

[m4dm4rtig4n]

Good luck with the overhaul.
I’ll stick with version 1.8.0 for now ^^

[m4dm4rtig4n]

I’m reopening my ticket because I’m trying to figure out how to apply a specific configuration to an APISIX route through annotations while still using the Ingress controller.

For example, adding a plugin to a route created by the Ingress controller.

[bzp2010]

@m4dm4rtig4n

I think you might want to consider alternative configuration methods, such as the Gateway API or Apisix CRD. This allows you to configure any plugin using PluginConfig or ApisixPluginConfig.

Even if we add annotations, they are not be considered as native extension points.