quarkus Kubernetes Extension should support Kubernetes Gateway API

Description

Today, the Quarkus Kubernetes extension already supports to generate Ingress configurations. It seems the Kubernetes Gateway API (https://gateway-api.sigs.k8s.io/) is the successor to the Ingress API. Furthermore, some Ingress implementations like kgateway (https://kgateway.dev/), which is a CNCF project, only support the newer Gateway API. Therefore, it would be great if there was an option to generate the required resources to use the Gateway API instead of the Ingress resources.

Implementation ideas

No response

Apr 23 '25 13:04 andreas-repp

/cc @geoand (kubernetes), @iocanel (kubernetes)

Apr 23 '25 13:04 quarkus-bot[bot]

Sounds reasonable. WDYT @iocanel ?

Apr 28 '25 09:04 geoand

Sounds good to me.

Apr 28 '25 09:04 iocanel

@andreas-eberle would you be willing to contribute such support?

Apr 28 '25 09:04 geoand

@andreas-eberle Does it mean, that currently it's not possible to use kubernetes gateway api with Quarkus containers?

Jul 30 '25 14:07 tolik93

No, it only means the kubernetes extension cannot generate Gateway API Specs for you. So you just have to write them yourself.

Jul 30 '25 15:07 andreas-repp