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

   ### Description
   
   According to the documentation I should be able to pass port's name in 
`servicePort` in ApisixRoute CRD. But if I  pass a name (ex. "http"). The 
controller complains:
   
   ```
   apisix-ingress-controller-97db6d444-6dcsl manager 2025-10-01T09:03:07.620Z   
 DPANIC    controllers.ApisixRoute    controller/apisixroute_controller.go:382  
  non-string key argument passed to logging, ignoring all later arguments    
{"invalid key": {"name":"portal-keyset-api","namespace":"pn-portal-bolek"}}     
                                                                                
                                                                                
       
   apisix-ingress-controller-97db6d444-6dcsl manager 2025-10-01T09:03:07.620Z   
 ERROR    controllers.ApisixRoute    controller/apisixroute_controller.go:382   
 Service    {"error": "port not found in service"}
   ```
   
   and do not update the routing. 
   
   I installed the chart with following values:
   
   ```
   apisix:
     etcd:
       enabled: false
     apisix:
       deployment:
         role: traditional
         role_traditional:
           config_provider: yaml
     service:
       type: ClusterIP
       externalTrafficPolicy: null
     ingress-controller:
       enabled: true
       config:
         provider:
           type: apisix-standalone
           sync_period: 1m
           init_sync_delay: 10s
       gatewayProxy:
         createDefault: true
       adminService:
         namespace: apisix
   ```
   
   Am I missing anything
   
   ### Environment
   
   I'm running:
   - apisix-ingress-controller:2.0.0-rc4
   - apisix:3.13.0-ubuntu
   
   Chart version: 2.11.6
   Kubernetes: 1.33
   


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