Skip to content

fix(install,helm): run kind Envoy as a NodePort, not hostNetwork - #145

Open
devopssquaddev wants to merge 2 commits into
mainfrom
fix/install-kind-no-hostnetwork
Open

devopssquaddev wants to merge 2 commits into
mainfrom
fix/install-kind-no-hostnetwork

Conversation

@devopssquaddev

Copy link
Copy Markdown
Owner

On a current kind (v0.33, kindnet v20260820), the local profiles' Envoy runs with hostNetwork: 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 MCP aigateway tool 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

  • Chart: optional gateway.envoyProxy.service.nodePorts.{http,https} (default 0), rendered as an EnvoyProxy Service patch. Rendering fails unless the Service is NodePort or LoadBalancer. 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.
  • Profiles: values-local, -fast and -perimeter use Envoy 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, so existing laptop clusters keep working.
  • CLI: hostNetworkGatewayCIDRs is filled only when the Envoy dataplane actually runs hostNetwork, not on every kind cluster.
  • Docs: a recreate note in the quickstart; updated agent-deploy wording.
  • Tests: NodePort render and TLS-off port checks, a test that the local profiles match 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:

  • fast and full install green
  • platform suite: 1246 passed, 90 skipped
  • FinServe: 34 passed, 2 skipped
  • UAT-12 passed with the self-check block overlay; it was deselected from the default-mode run because the default self-check only logs

Existing kind users: kind delete cluster --name zelkor, then ./install.sh.

🤖 Generated with Claude Code

devopssquaddev and others added 2 commits November 18, 2026 14:18
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>
@cloudflare-workers-and-pages

Copy link
Copy Markdown

🚀 Deploying Preview to Cloudflare 🚀

Preview Deployments by commit

Status Deployment URL Commit Updated (UTC) See this deployment's details
  • Build: Success ✅

View logs ↗
No Preview URL. Enable ↗ dc8f3f3 2026-11-18T14:05:54.708Z Visit the dashboard ↗

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant