docs(ha-k8s): guide for using Istio as the Gateway API controller - #1741
Open
as51340 wants to merge 1 commit into
Open
docs(ha-k8s): guide for using Istio as the Gateway API controller#1741as51340 wants to merge 1 commit into
as51340 wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
as51340
added
the
feature
as51340
force-pushed
the
docs/ha-istio-gateway
branch
from
August 27, 2026 11:42
fb622ca to
dc8101d
Compare
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.
Release note
Added a guide for exposing the Memgraph HA Helm chart through Istio as the Gateway API controller: Helm-based Istio installation (experimental Gateway API CRDs +
istio-base+istiod), the requiredPILOT_ENABLE_ALPHA_GATEWAY_API=trueflag with its misleading failure mode explained (GatewayProgrammed=Truebut TCPRoutes get no status and connections time out), client connection guidance (bolt://vsneo4j://routing with anexternal-dnshostname), and a note on sidecar-injecting Memgraph pods (native sidecars vs excluding thecluster-setupJob).Related product PRs
examples/gateway/istio-values.yaml)Checklist:
bugfixorfeaturelabel, based on the product PR type you're documenting