Gateway API 1.1.0 released

[fmunteanu]

Is there an existing issue for this?

• I have searched the existing issues

What happened?

Gateway API 1.1.0 was released yesterday. I was wondering if the developers can validate if the experimental install is still the proper way to implement Gateway API, with Cilium. I'm going to test the new release and report back.

Cilium Version

1.15.4

Kernel Version

6.8.0-1004-raspi

Kubernetes Version

1.29.4

Regression

No response

Sysdump

No response

Relevant log output

No response

Anything else?

No response

Cilium Users Document

• Are you a user of Cilium? Please add yourself to the Users doc

Code of Conduct

• I agree to follow this project's Code of Conduct

[fmunteanu]

I performed a fresh cluster installation and the experimental install is still required. The standard install renders the Gateway with HTTPRoute, non functional.

[vehagn]

I don’t think the experimental Gateway CRDs are required for basic functionality, that’s only for the experimental features like the spec.infrastructure.annotations to e.g. set the IP for the Gateway Service.

The Cilium docs on Gateway API suggest the standard install of both Gateway and HTTPRoute.

Not sure if Cilium has much say in graduating that field to the standard install of Gateway API.

[fmunteanu]

@vehagn we can check it together but on my initial tests, a combination of Gateway + HTTPRoute would fail to load a secure webpage, when installing the 1.1.0 standard install. Once I switch to experimental, everything works as expected.

[sayboras]

There is some works required for Gateway API v1.1.0, the details can be found in #32492

[fmunteanu]

@sayboras I only use the HTTPRoute, I believe this should not be an issue for me upgrading to 1.1.0 release?

[networkhermit]

Seems related, might be a good opportunity to remove the hard requirements of experimental alpha/beta crds, as future releases of gateway api could break cilium-operator too.

kubernetes-sigs/gateway-api#3075 (comment)

Link #32539

[vehagn]

@vehagn we can check it together but on my initial tests, a combination of Gateway + HTTPRoute would fail to load a secure webpage, when installing the 1.1.0 standard install. Once I switch to experimental, everything works as expected.

@fmunteanu Could you please share the Gateway + HTTPRoute you're testing with? Then I can test similar resources on my end.

[fmunteanu]

@vehagn please look at my Hubble setup, as example. I have a gateway and two routes, http and https.

[squeed]

Should we close this in favor of #32492, @sayboras?

[fmunteanu]

@sayboras some small note on the current stable Cilium Gateway API documentation. You make reference of installing specific manifests, while the official documentation refers to a single one-liner.

I'm only using HTTPRoute with Cilium and the standard install one-liner fails to produce a functional URL, while the experimental install does. Can the documentation be improved in this area? I believe performing a one-liner installation is simplified, however, the current standard install limitations must be accounted, with this approach.

I'm wondering what is your input on this?