You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@apisix.apache.org by "rhysxevans (via GitHub)" <gi...@apache.org> on 2024/03/21 00:14:48 UTC

[I] Ability to set Plugin Priorities [apisix-ingress-controller]

rhysxevans opened a new issue, #2191:
URL: https://github.com/apache/apisix-ingress-controller/issues/2191

   ### Description
   
   Hi, as a user I would like to use the `ApisixRoute` api to set the plugin priorities as per https://docs.api7.ai/apisix/reference/plugin-common-configurations#_metapriority , this should probably include via the `ApisixPluginConfig` api
   
   Any help is appreciated


-- 
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: notifications-unsubscribe@apisix.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] request help: how to set plugin priorities [apisix-ingress-controller]

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.

github-actions[bot] commented on issue #2191:
URL: https://github.com/apache/apisix-ingress-controller/issues/2191#issuecomment-2415542110

   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.


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] request help: how to set plugin priorities [apisix-ingress-controller]

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.

github-actions[bot] closed issue #2191: request help: how to set plugin priorities
URL: https://github.com/apache/apisix-ingress-controller/issues/2191


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] request help: how to set plugin priorities [apisix-ingress-controller]

Posted by "kayx23 (via GitHub)" <gi...@apache.org>.

kayx23 commented on issue #2191:
URL: https://github.com/apache/apisix-ingress-controller/issues/2191#issuecomment-2172847638

   Can you try something like this:
   
   ```
   apiVersion: apisix.apache.org/v2
   kind: ApisixRoute
   metadata:
     name: httpbin-route
   spec:
     http:
       - name: httpbin-route
         match:
           paths:
             - /ip
         backends:
           - serviceName: httpbin
             servicePort: 80
         plugins:
         - name: limit-count
           enable: true
           config:
             _meta:
               priority: 1200
             time_window: 10
             count: 2
             rejected_code: 429
   ```
   
   and check in the apisx pod if the `_meta.proprity` is updated? You can port forward 9180 and  `curl "http://127.0.0.1:9180/apisix/admin/routes" -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1'`.


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] request help: how to set plugin priorities [apisix-ingress-controller]

Posted by "github-actions[bot] (via GitHub)" <gi...@apache.org>.

github-actions[bot] commented on issue #2191:
URL: https://github.com/apache/apisix-ingress-controller/issues/2191#issuecomment-2351891439

   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 dev@apisix.apache.org list. Thank you for your contributions.


-- 
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: notifications-unsubscribe@apisix.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org