cai200631 commented on issue #1167:
URL: 
https://github.com/apache/apisix-ingress-controller/issues/1167#issuecomment-1188975148

   > Yes! We can use the PluginConfig annotation on the Ingress resource to 
bind any APISIX plugin to the Ingress resource.
   > 
   > you can refer to 
https://github.com/apache/apisix-ingress-controller/blob/master/docs/en/latest/concepts/annotations.md#use-apisixpluginconfig
   > 
   > This feature will be introduced in this month's v1.5 release. Implemented 
in #1139
   
   I am confused,  is apisixpluginconfig can bind traffic-split now?  or I can 
bind traffic-split plugin to apisixpluginconfig when V1.5 is released ? 
   
   
   I have tried as follows:
   
   1. declare  an ApisixPluginConfig: 
   
   apiVersion: apisix.apache.org/v2beta3
   kind: ApisixPluginConfig
   metadata:
     name: traffic-split
     namespace: test-beijing
   spec:
     plugins:
     - name: traffic-split
       enable: true
       config:
        rules:
         - match:
           - vars:
               - front-traffic-env
               - ==
               - test-beijing
   
   2. declare an Ingress: 
   
   apiVersion: networking.k8s.io/v1
   kind: Ingress
   metadata:
     name: um-qingzhou-fe-70otk2cqeal71rq10wdyb1463
     namespace: test-beijing
     annotations:
       k8s.apisix.apache.org/plugin-conifg-name: "traffic-split"
     labels:
       deployment: um-qingzhou-fe
       env: test-beijing
       host: test.demo.com
   spec:
     ingressClassName: apisix
     rules:
       - host: qingzhou.baijia.com
         http:
           paths:
             - path: /
               pathType: Prefix
               backend:
                 service:
                   name: svc-arch-fe-general-test-service
                   port:
                     number: 80
   
   
   
   but when I curl add an header  'front-traffic-env:test-beijing' http:// 
test.demo.com/index.html,  it is not working;
   


-- 
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]

Reply via email to