Skip to content

fix(proxy): NO_PROXY covers the cloud metadata IP (chart + both installers)#337

Open
LukasWodka wants to merge 1 commit into
developfrom
fix/no-proxy-metadata-ip
Open

fix(proxy): NO_PROXY covers the cloud metadata IP (chart + both installers)#337
LukasWodka wants to merge 1 commit into
developfrom
fix/no-proxy-metadata-ip

Conversation

@LukasWodka

@LukasWodka LukasWodka commented Jul 11, 2026

Copy link
Copy Markdown
Contributor

Summary

The auto-augmented NO_PROXY lists omitted the cloud metadata IP 169.254.169.254, so on proxy tenants metadata traffic would be sent to the corporate proxy (broken IMDS access; instance credentials transiting a middlebox for no reason). Adds the IP to the chart helper (tracebloc.proxyEnv), the bash installer defaults (_augment_no_proxy), and the Windows defaults (Get-EffectiveNoProxy) — the three lists stay in lockstep — and regenerates manifest.sha256 for the two touched scripts. Chart bumped 1.9.3 → 1.9.4.

This is the chart/installer half of backend#803 item J; the runtime half (jobs-manager/ingestor NO_PROXY strings) ships separately in client-runtime alongside the #120 fix.

Related

Ref tracebloc/backend#803 (item J). Ref tracebloc/client-runtime#120.

Type of change

  • Bug fix

Test plan

  • helm unittest client: 25 suites / 267 tests pass, including the three updated exact-value NO_PROXY assertions in client/tests/proxy_env_test.yaml
  • bats scripts/tests/cluster.bats: 27 tests pass, including a new 169.254.169.254 assertion on _augment_no_proxy
  • Pester assertion added to Get-EffectiveNoProxy (runs in CI's Windows job)
  • scripts/gen-manifest.sh regenerated — exactly the cluster.sh + install-k8s.ps1 digests changed; CI --check gate stays green
  • Note: helm lint client fails on develop already (schema requires non-empty clientId/clientPassword) — pre-existing, unrelated

Checklist

  • Tests added / updated and passing locally
  • No secrets / credentials in the diff

🤖 Generated with Claude Code


Note

Low Risk
Narrow proxy-bypass list change with installer/chart parity and test coverage; no auth or data-model changes.

Overview
Adds 169.254.169.254 (link-local cloud metadata) to the auto-augmented NO_PROXY lists so corporate-proxy tenants do not send IMDS traffic through the HTTP proxy.

The same default is applied in tracebloc.proxyEnv (Helm), TB_NO_PROXY_DEFAULTS / _augment_no_proxy (bash installer), and Get-EffectiveNoProxy (Windows installer), with helm unittest, bats, and Pester expectations updated. Chart version is bumped 1.9.3 → 1.9.4, and scripts/manifest.sha256 is refreshed for the touched installer scripts.

Reviewed by Cursor Bugbot for commit 60a1dd3. Bugbot is set up for automated code reviews on this repo. Configure here.

The auto-augmented NO_PROXY lists (chart tracebloc.proxyEnv helper,
bash _augment_no_proxy defaults, Windows Get-EffectiveNoProxy defaults)
omitted 169.254.169.254 — behind a corporate proxy, cloud metadata
lookups would be routed through the external proxy (broken IMDS access
and an unnecessary place for instance credentials to transit).

Add the IP to all three lists in lockstep, pin it in the bats + Pester
+ helm-unittest expectations, regenerate manifest.sha256 for the two
touched installer scripts, bump chart 1.9.3 -> 1.9.4.

Ref tracebloc/backend#803 (item J), tracebloc/client-runtime#120

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.

2 participants