mikkel1156 opened a new issue, #2782:
URL: https://github.com/apache/apisix-ingress-controller/issues/2782
### Current Behavior
I am getting "404 Route Not Found" after updating the APISIX helm chart to
latest version, and after testing it is only happening on the latest 2.1.0
release.
It is creating the route, but is unable to match the request to it. I did a
output of both configurations between the versions, and the only difference is
the server_port in vars as introduced in #2703
Working route:
```json
{
"uris": [
"/",
"/*"
],
"priority": 32338085888,
"service_id": "a2594164",
"labels": {
"k8s/controller-name": "apisix.apache.org/apisix-ingress-controller",
"k8s/kind": "HTTPRoute",
"k8s/namespace": "forgejo",
"manager-by": "apisix-ingress-controller",
"k8s/name": "forgejo"
},
"id": "47600540",
"modifiedIndex": 1780683114135,
"status": 1,
"name": "forgejo_forgejo_0-0"
}
```
Route in new version that is not being matched:
```json
{
"priority": 32338085888,
"vars": [
[
"server_port",
"in",
[
"80",
"443"
]
]
],
"modifiedIndex": 1780682959811,
"status": 1,
"name": "forgejo_forgejo_0-0",
"service_id": "a2594164",
"id": "47600540",
"labels": {
"k8s/namespace": "forgejo",
"k8s/kind": "HTTPRoute",
"k8s/name": "forgejo",
"manager-by": "apisix-ingress-controller",
"k8s/controller-name": "apisix.apache.org/apisix-ingress-controller"
},
"uris": [
"/",
"/*"
]
},
```
### Expected Behavior
Route would be matched and traffic would be proxied.
### Error Logs
None found.
### Steps to Reproduce
I'll put some details of the environment here (note: I am changing my actual
domain to example.com below):
```yaml
apiVersion: gateway.networking.k8s.io/v1
kind: Gateway
metadata:
annotations:
cert-manager.io/cluster-issuer: letsencrypt
name: apisix
namespace: apisix
spec:
gatewayClassName: apisix
infrastructure:
parametersRef:
group: apisix.apache.org
kind: GatewayProxy
name: apisix-config
listeners:
- allowedRoutes:
namespaces:
from: All
name: http
port: 80
protocol: HTTP
- allowedRoutes:
namespaces:
from: All
hostname: '*.example.com'
name: https
port: 443
protocol: HTTPS
tls:
certificateRefs:
- group: ""
kind: Secret
name: gateway-example-com
mode: Terminate
```
HTTPRoute:
```yaml
apiVersion: gateway.networking.k8s.io/v1
kind: HTTPRoute
metadata:
name: forgejo
namespace: forgejo
spec:
hostnames:
- git.example.com
parentRefs:
- group: gateway.networking.k8s.io
kind: Gateway
name: apisix
namespace: apisix
rules:
- backendRefs:
- group: ""
kind: Service
name: forgejo
port: 80
weight: 1
filters: []
matches:
- path:
type: PathPrefix
value: /
```
Helm values:
```yaml
service:
type: "LoadBalancer"
externalTrafficPolicy: Local
etcd:
enabled: false
ingress-controller:
enabled: true
config:
enableHTTP2: true
provider:
type: apisix-standalone
apisix:
adminService:
namespace: apisix
gatewayProxy:
createDefault: false
apisix:
pluginAttrs:
redirect:
https_port: 443
admin:
allow:
ipList:
- 127.0.0.1/24
- 10.0.0.0/8
ssl:
enabled: true
deployment:
role: traditional
role_traditional:
config_provider: yaml
```
```
### Environment
- APISIX Ingress controller version: 2.1.0
- Kubernetes cluster version (run `kubectl version`): 1.34.1
- OS version if running APISIX Ingress controller in a bare-metal
environment (run `uname -a`): NixOS 25.11
--
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]
