Patryk Małek

As mentioned in the comment thread in https://github.com/Kong/kubernetes-ingress-controller/pull/7466#discussion_r2128299713 there is still some work to be done (at the very least in adjusting the sample manifest). @tao12345666333 has more context around...

@tao12345666333 #6129 is this issue here 😅

Waiting for #8560 to merge.

> Manager in envtest could configure Kong deployed in a docker container (could be spawned with [testcontainers](https://github.com/testcontainers/testcontainers-go), we could trick Gateway Discovery to work as expected by injecting `EndpointSlices` pointing...

> There is a work around for this as main isn't versioned along with tools/setupenv-tools. [#1670 (comment)](https://github.com/kubernetes-sigs/controller-runtime/issues/1670#issuecomment-1010602287) I've also hit that issue and the workaround while working it's cumbersome to...

#1131 will bump the default kong gateway version 3.7. You can use 3.8 by specifying it via `values.yaml` if you so desire.

https://github.com/Kong/charts/releases/tag/kong-2.42.0 already ships with 3.7 as default. You can still set the 3.8 using `values.yaml`. Hope that helps.

@mlalam TLSListener is not supported yet as per https://github.com/Kong/gateway-operator/blob/20f084194be07bb17d149e0b1b68e603e05a9ccd/controller/gateway/controller_reconciler_utils.go#L524-L534 and the fact that #64 is still open. You should observe something like in your Gateway's status: ``` conditions: - lastTransitionTime:...

> thanks @pmalek . I see the open ticket #64 hasn't been touched for 8 years. Is it in the roadmap for KGO in near future? Cannot speak for this...

Hi @mlalam Sorry for the delayed reponse. I only had time to check 1 thing which is whether [the example manifest for TLSRoute passthrough using Gateway API](https://github.com/Kong/kubernetes-ingress-controller/blob/822816853847c23fc9757b54d06d231deca55095/examples/gateway-tlsroute.yaml) would make sense...