Richard0706 opened a new issue, #10608:
URL: https://github.com/apache/apisix/issues/10608

   ### Description
   
   I created a rule like this:
   ```
   spec:
     ingressClassName: apisix
     rules:
     - host: apisix-dashboard.mytest.com
       http:
         paths:
         - backend:
             service:
               name: apisix-dashboard
               port:
                 number: 80
           path: /*
           pathType: ImplementationSpecific
   status:
     loadBalancer: {}
   ```
   There is nothing wrong with these, I want to use the elasticsearch-logger 
plugin, so I executed a command like this:
   ```
   curl http://127.0.0.1:9180/apisix/admin/routes/d6a65f62 \
   -H 'X-API-KEY: edd1c9f034335f136f87ad84b625c8f1' -X PUT -d '
   {
     "uris": [
       "/*"
     ],
     "name": "ing_apisix_apisix-dashboard_71cd8a6c",
     "desc": "Created by apisix-ingress-controller, DO NOT modify it manually",
     "host": "apisix-dashboard.mytest.com",
       "plugins":{
           "elasticsearch-logger":{
               "endpoint_addr":"http://192.168.1.5:9200";,
               "field":{
                   "index":"services-apisix-dashboard"
               }
           }
       },  
     "upstream_id": "6624cd4a",
     "labels": {
       "managed-by": "apisix-ingress-controller"
     },
     "status": 1
   }'
   ```
   **When I just finished executing this, everything was normal and I could see 
the data in the es index, but after a few minutes, the rule to enable the 
elasticsearch-logger plugin disappeared.**
   **I need your help. Most of my routing rules come from Kubernetes ingress. 
How can I enable plug-ins on the already created rules so that they will always 
take effect?**
   
   ### Environment
   
   - APISIX version (run `apisix version`): 3.2
   - Operating system (run `uname -a`): kubernetes v1.21.14
   


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