app.ingress.tls.enabled: ingress' $servicePort should not depend on it but on `kong.proxy.tls.enabled`

Warnings during standard install

Ah that is working as expected. the new "Wave AI" side panel currently does not allow for local models or BYOK while it is is in beta. I only have an OpenAI "responses" API set up right now, which is not compatible with the "completions" api that we were using before. I also don't have adapters set up for other APIs yet either. This is all in the works though and will be coming out with future patch releases over the next couple of weeks.

Failed to pull kong:3.9: helm chart use short name: not anymore supported with cri-o v1.34

Push Helm chart to an OCI registry

Add Gateway API HTTPRoute support to Helm chart

[CRITICAL][BUG] dashboards broken due to bad cpu limits in the helm chart

authenticating with a google cloud access token fails successfully (500 OK)

Kong pod doesn't start

Allow searching CRDs