AlinsRan commented on issue #2708:
URL: 
https://github.com/apache/apisix-ingress-controller/issues/2708#issuecomment-3832576013

   Thank you for reporting this issue and for the details you’ve provided.
   
   We attempted to reproduce the problem in our local environment using the 
following steps:
   
   > 1. deploy apisix and apisix-ingress-controller:
   > 
   > ```shell
   > helm install apisix \
   >   --namespace ingress-apisix \
   >   --create-namespace \
   >   --set apisix.deployment.role=traditional \
   >   --set apisix.deployment.role_traditional.config_provider=yaml \
   >   --set etcd.enabled=false \
   >   --set ingress-controller.enabled=true \
   >   --set ingress-controller.config.provider.type=apisix-standalone \
   >   --set ingress-controller.apisix.adminService.namespace=ingress-apisix \
   >   --set ingress-controller.gatewayProxy.createDefault=true \
   >   apisix/apisix
   > ```
   > 
   > 2. deploy httpbin upstream:
   > 
   > ```shell
   > kubectl apply -f 
https://raw.githubusercontent.com/apache/apisix-ingress-controller/refs/heads/v2.0.0/examples/httpbin/deployment.yaml
   > ```
   > 
   > 3. apply route
   > 
   > ```yaml
   > apiVersion: apisix.apache.org/v2
   > kind: ApisixRoute
   > metadata:
   >   name: getting-started-ip
   > spec:
   >   ingressClassName: apisix
   >   http:
   >     - name: getting-started-ip
   >       match:
   >         paths:
   >           - /ip
   >       backends:
   >         - serviceName: httpbin
   >           servicePort: 80
   > ```
   > 
   > 4. scale httpbin to 4 replicas:
   > 
   > ```shell
   > kubectl scale deployment httpbin-deployment --replicas=4
   > ```
   > 
   > Check the upstream configuration of the data plane:
   > 
   > ```shell
   > curl localhost:9180/apisix/admin/configs -H "X-API-Key: 
edd1c9f034335f136f87ad84b625c8f1" -s | jq .upstreams
   > [
   >   {
   >     "id": "ad735c2f",
   >     "type": "roundrobin",
   >     "labels": {
   >       "managed-by": "apisix-ingress-controller"
   >     },
   >     "name": "default_getting-started-ip_0",
   >     "nodes": [
   >       {
   >         "port": 80,
   >         "host": "10.244.0.7",
   >         "weight": 100
   >       },
   >       {
   >         "port": 80,
   >         "host": "10.244.0.15",
   >         "weight": 100
   >       },
   >       {
   >         "port": 80,
   >         "host": "10.244.0.14",
   >         "weight": 100
   >       },
   >       {
   >         "port": 80,
   >         "host": "10.244.0.13",
   >         "weight": 100
   >       }
   >     ],
   >     "modifiedIndex": 1769998251570
   >   }
   > ]
   > ```
   > 
   > Check the logs after sending the request:
   > 
   > <img width="2210" height="408" alt="Image" 
src="https://github.com/user-attachments/assets/b0b96c65-44e5-43a0-806d-2751c590da2a";
 />
   > 
   > 
   > 5. scale httpbin to 1 replicas:
   > 
   > ```shell
   > kubectl scale deployment httpbin-deployment --replicas=1
   > ```
   > 
   > Check the upstream configuration of the data plane:
   > 
   > ```shell
   > curl localhost:9180/apisix/admin/configs -H "X-API-Key: 
edd1c9f034335f136f87ad84b625c8f1" -s | jq .upstreams
   > [
   >   {
   >     "id": "ad735c2f",
   >     "type": "roundrobin",
   >     "labels": {
   >       "managed-by": "apisix-ingress-controller"
   >     },
   >     "name": "default_getting-started-ip_0",
   >     "nodes": [
   >       {
   >         "port": 80,
   >         "host": "10.244.0.7",
   >         "weight": 100
   >       }
   >     ],
   >     "modifiedIndex": 1769998390864
   >   }
   > ]
   > ```
   > 
   > Check the logs after sending the request:
   > 
   > <img width="2274" height="194" alt="Image" 
src="https://github.com/user-attachments/assets/9411d88c-656a-4662-b8ec-11aa250495d8";
 />
   
   
   However, under these conditions, we were **unable to reproduce the issue**.
   
   To help us investigate further, could you please provide some additional 
information?
   
   ### Minimal Reproducible Example
   - A simplified configuration or setup that can reliably reproduce the issue
   - If applicable, a sample request along with the expected and actual behavior
   
   ### Logs or Error Output
   - Relevant error or warning logs
   - Stack traces or additional diagnostic output, if available
   
   ### Additional Context
   - Whether the issue occurs consistently or intermittently
   - Any specific conditions under which the issue is more likely to occur
   
   With this information, we should be able to narrow down the root cause more 
effectively.  
   Thanks again for your report, and we appreciate your help in moving this 
forward.


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