Q - Gateway API artefacts support

[VaclavK]

Hi,

wondering - is the "built in " support for Gateway API and associated artefacts - e.g. HttpRoute in the pipeline? So far we have had full support for "old style" ingress but with K8S moving to Gateway API it would be great not to have to treat this as custom objects...

[IvanJosipovic]

Hey,

Gateway API is still not a "native" Kubernetes API, it's a Custom Resource Definition. I have the models published in this Nuget https://www.nuget.org/packages/KubernetesCRDModelGen.Models.gateway.networking.k8s.io/

It can be used with the Generic client.

[VaclavK]

Hi, I am aware of the CRD aspect (still)

thank you for the pointer to the nuget package - very helpful

I will use the model as a DTO and not hook it up/watch via generic client as there I would be subject to cluster vs namespaced split and I want to watch all of them (of specific group etc.)

but I can still hook it up as WatchListCustomObjectForAllNamespacesAsync and then deserialize tuple item returned using your model so I don't have to write/generate my own.

this is I suppose a design decision whether you would "jump the gun" and treat it as a native object already or wait... I would argue that this api might be a good candidate for that, but I will understand why this would not be considered either to keep both sides aligned - admittedly I am not as close to following K8S design decisions/history as you guys

thanks for the reply