bug: annotation k8s.apisix.apache.org/plugin-config-name not interpreted

[kladiv]

Current Behavior

Hello,
according to #2559, it seems that annotation k8s.apisix.apache.org/plugin-config-name does still not work in latest AIC version.

Expected Behavior

Annotation correctly interpreted

Error Logs

Plugins are not interpreted

Steps to Reproduce

1. Deploy an Ingress with an annotation

metadata:
  annotations:
    k8s.apisix.apache.org/plugin-config-name: my-plugin

2. Check the Ingress resource with kubectl… the annotation is present
3. Observe that the plugin is not attached to the APISIX route

Environment

Helm Chart: apisix/apisix v2.13.0 (appVersion 3.15.0, AIC appVersion 2.0.1)
Kubernetes RKE2: v1.35.0+rke2r1

[Baoyuantop]

Hi @kladiv, the controller logic is designed to look for an ApisixPluginConfig resource with the specified name within the same namespace as your Ingress resource.For the annotation to be interpreted correctly, please ensure the following conditions are met:

1. ApisixPluginConfig Exists: You must have an ApisixPluginConfig resource created in the same Kubernetes namespace as your Ingress resource. The name of this ApisixPluginConfig must exactly match the value you provided in the annotation.

# Must be in the same namespace as your Ingress
apiVersion: apisix.apache.org/v2
kind: ApisixPluginConfig
metadata:
  name: my-plugin # This name must match the annotation value
spec:
  ingressClassName: apisix
  plugins:
    - name: some-plugin
      enable: true
      config:
        # ... plugin configuration

2. Matching ingressClassName: If your ApisixPluginConfig specifies an ingressClassName in its spec, it must match the ingressClassName of your Ingress resource. If the Ingress resource doesn't explicitly define an ingressClassName, it will use the default one for the cluster. The controller will only apply the plugin configuration if the class names match.

Could you please verify that the ApisixPluginConfig resource named my-plugin exists in the same namespace as your Ingress and that their ingressClassName settings are compatible? If the issue persists after confirming these points, could you please provide the YAML manifests for both your Ingress and ApisixPluginConfig resources? That would be very helpful for further troubleshooting.

[kladiv]

Hi @Baoyuantop,
i found the misconfiguration in my YAML. It's working now thanks

Just an additional question: how can plugins order be set? Is something we can control?
Thank you

[Baoyuantop]

Refer to https://apisix.apache.org/docs/apisix/terminology/plugin/#plugins-execution-order