mayankmurari opened a new issue, #2484:
URL: https://github.com/apache/apisix-ingress-controller/issues/2484
### Issue description
### Description
When using APISIX Ingress Controller 2.0.0-rc1 in standalone mode (without
etcd), Gateway API resources (GatewayClass, Gateway, HTTPRoute) are not being
properly processed. The Gateway remains in "Unknown" status with "Waiting for
controller" message, and routes defined with HTTPRoute are not being created in
APISIX.
### Observed Behavior
1. GatewayClass shows "Unknown" status with "Waiting for controller" message
2. Gateway shows "Unknown" status with "Waiting for controller" message
3. HTTPRoute is created but does not have a status field
4. Accessing the route returns a 404 error: `{"error_msg":"404 Route Not
Found"}`
### Questions
1. Is Gateway API fully supported in standalone mode with APISIX Ingress
Controller 2.0.0-rc1?
2. Are there additional configuration steps needed to enable Gateway API
support in standalone mode?
### Deployment Configurations
APISIX:
```yaml
deployment:
mode: standalone
role: "traditional"
role_traditional:
config_provider: "yaml"
```
APISIX Ingress Controller
```yaml
ingress-controller:
enabled: true
config:
logLevel: info
kubernetes:
enableGatewayAPI: true
ingressClass: apisix
provider:
type: apisix-standalone
sync_period: 1s
init_sync_delay: 1m
apisix:
default:
adminApiVersion: v3
baseUrl:
http://apisix-admin.ingress-apisix.svc.cluster.local:9180/apisix/admin
adminKey: admin
gatewayProxy:
createDefault: true
provider:
type: ControlPlane
controlPlane:
endpoints:
- http://apisix-admin.ingress-apisix.svc.cluster.local:9180
auth:
type: AdminKey
adminKey:
value: "admin"
serviceAccount:
create: true
annotations: {}
rbac:
create: true
```
### Ingress Controller Logs (relevant portions)
```
2025-07-18T13:25:05.393Z INFO controller-runtime
controller/controller.go:175 Starting EventSource {"controller":
"gatewayclass", "controllerGroup": "gateway.networking.k8s.io",
"controllerKind": "GatewayClass", "source": "kind source: *v1.GatewayClass"}
2025-07-18T13:25:05.393Z INFO controller-runtime
controller/controller.go:183 Starting Controller {"controller": "gatewayclass",
"controllerGroup": "gateway.networking.k8s.io", "controllerKind":
"GatewayClass"}
2025-07-18T13:25:05.393Z INFO controller-runtime
controller/controller.go:175 Starting EventSource {"controller": "gateway",
"controllerGroup": "gateway.networking.k8s.io", "controllerKind": "Gateway",
"source": "kind source: *v1.Gateway"}
2025-07-18T13:25:05.393Z INFO controller-runtime
controller/controller.go:175 Starting EventSource {"controller": "httproute",
"controllerGroup": "gateway.networking.k8s.io", "controllerKind": "HTTPRoute",
"source": "kind source: *v1.HTTPRoute"}
2025-07-18T13:25:05.694Z INFO controller-runtime
controller/controller.go:217 Starting workers {"controller": "gatewayclass",
"controllerGroup": "gateway.networking.k8s.io", "controllerKind":
"GatewayClass", "worker count": 1}
2025-07-18T13:25:05.697Z INFO controller-runtime
controller/controller.go:217 Starting workers {"controller": "httproute",
"controllerGroup": "gateway.networking.k8s.io", "controllerKind": "HTTPRoute",
"worker count": 1}
2025-07-18T13:25:05.700Z INFO controller-runtime
controller/controller.go:217 Starting workers {"controller": "gateway",
"controllerGroup": "gateway.networking.k8s.io", "controllerKind": "Gateway",
"worker count": 1}
```
## GatewayClass Status
```
Status:
Conditions:
Last Transition Time: 1970-01-01T00:00:00Z
Message: Waiting for controller
Reason: Pending
Status: Unknown
Type: Accepted
Events: <none>
```
### Environment
### Environment
- APISIX version: 3.13.0-debian
- APISIX Ingress Controller version: 2.0.0-rc1
- Kubernetes version: v1.31.10
- Deployment method: Helm chart
- Operating mode: Standalone (without etcd)
--
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-unsubscr...@apisix.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
