Repository navigation
fix(install,helm): run kind Envoy as a NodePort, not hostNetwork - #145
Open
devopssquaddev wants to merge 2 commits into
Open
devopssquaddev wants to merge 2 commits into
devopssquaddev wants to merge 2 commits into
Conversation
Current kindnet (kind v0.33) does not match a host-network Envoy pod with
NetworkPolicy namespace selectors, so every policy-restricted pod (MCP
servers, agents, sandbox) loses the gateway. Seen on kind with Kubernetes
1.36.4: the MCP aigateway tool timed out connecting to the gateway.
- chart: optional gateway.envoyProxy.service.nodePorts.{http,https}
(default 0) rendered as an EnvoyProxy Service patch; fails unless the
Service is NodePort or LoadBalancer
- local, local-fast and local-perimeter profiles: Envoy Service NodePort
30080/30443 instead of hostNetwork; kind-config.yaml maps host
8088/8443 to those node ports
- install-engine: an existing cluster with the old 8088->10080 mapping
keeps hostNetwork and warns to recreate it
- CLI: hostNetworkGatewayCIDRs only when the Envoy dataplane actually
runs hostNetwork, not on every kind cluster
- docs: quickstart recreate note; agent-deploy wording
Spec: internal plan/architecture_ingress_exposure.md (2026-11-18 row).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A strategic-merge entry for port 443 without an HTTPS listener adds an unnamed Service port; Kubernetes rejects the Service and Envoy Gateway creates no dataplane (kind fast install: Langfuse seed could not resolve the MCP ExternalName). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
🚀 Deploying Preview to Cloudflare 🚀Preview Deployments by commit
|
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
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.
On a current kind (v0.33, kindnet
v20260820), the local profiles' Envoy runs withhostNetwork: true, so its pod IP is the node IP. NetworkPolicy namespace and pod selectors don't match a host-network pod, and the new kindnet drops the traffic. So every policy-restricted pod (MCP servers, agents, the sandbox) loses the gateway. Seen on kind with Kubernetes 1.36.4: the MCPaigatewaytool timed out connecting to the gateway, and the FinServe suite hung.This goes back to the NodePort shape that the ingress spec already describes for kind.
Changes
gateway.envoyProxy.service.nodePorts.{http,https}(default0), rendered as an EnvoyProxy Service patch. Rendering fails unless the Service isNodePortorLoadBalancer. The HTTPS port is patched only when TLS is on; a patch entry for a port the Gateway doesn't have adds an unnamed Service port, Kubernetes rejects the Service, and no dataplane is created.values-local,-fastand-perimeteruse Envoy NodePort 30080/30443 instead ofhostNetwork.kind-config.yamlmaps host 8088/8443 to those node ports.8088→10080mapping keepshostNetworkand warns to recreate it, so existing laptop clusters keep working.hostNetworkGatewayCIDRsis filled only when the Envoy dataplane actually runshostNetwork, not on every kind cluster.agent-deploywording.kind-config.yaml, a guard test for the new setting, and a CLI test for a NodePort Envoy.Verified on tes2 (kind v0.33.0, Kubernetes 1.36.4, Helm v4.3.0), together with #144:
Existing kind users:
kind delete cluster --name zelkor, then./install.sh.🤖 Generated with Claude Code