Repository navigation
Conversation
The chart can only expose Qdrant through an Ingress. Clusters moving to Gateway API have no way to route to the service without a hand-written HTTPRoute outside the release. Add an opt-in httpRoute values block that renders an HTTPRoute (API version gateway.networking.k8s.io/v1) pointing at the Qdrant service. It can be used alongside or instead of the Ingress. parentRefs is required when the route is enabled, because a route without a parent attaches nowhere. TLS is configured on the Gateway listener, so there is no tls value. Assisted-by: LLM Signed-off-by: Aleksei Sviridkin <f@lex.la>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an opt-in
httpRoutevalues block that renders a Gateway API HTTPRoute for the Qdrant service. It is off by default and can be enabled next to the Ingress or instead of it.I run Qdrant through Cozystack, a CNCF project that is moving its service exposure to Gateway API. Right now the chart can't route to Qdrant without a hand-written HTTPRoute outside the release.
parentRefsis required when the route is enabled, and the template fails without it. There is notlsvalue, since TLS is terminated on the Gateway listener.I didn't bump
Chart.yamlor the changelogs. Recent feature PRs leave that to the release.