Skip to content

feat(helm): configure the egress proxy log level on release-1.0 - #124

Closed
TarasLykhenko wants to merge 3 commits into
kagent-dev:release-1.0from
TarasLykhenko:backport/release-1.0-egress-log-level
Closed

TarasLykhenko wants to merge 3 commits into
kagent-dev:release-1.0from
TarasLykhenko:backport/release-1.0-egress-log-level

Conversation

@TarasLykhenko

Copy link
Copy Markdown

Backport #119 to release-1.0 so installations can configure the shared egress proxy's RUST_LOG without patching its Deployment.

Cherry-pick the three original signed commits, preserving their DCO sign-offs. No conflicts or additional changes. The combined patch ID matches merged commit 65fcc744ed74b643cc3cccfa2f921d35f169903c.

Expose atenetEgress.agentgateway.logLevel, defaulting to info, with support for filters such as info,agentgateway=debug. Keep the Helm e2e installation at debug because its networking tests assert the debug-level CONNECT log.

Checks:

  • All 46 chart tests pass.
  • All three charts pass Helm lint.
  • Committed-manifest verification and git diff --check pass.
  • Full Go and cluster e2e suites were not rerun locally for this backport.

AI use: AI-assisted backport, diff review, local checks, and PR preparation.

Signed-off-by: TarasLykhenko <18290033+TarasLykhenko@users.noreply.github.com>
Signed-off-by: TarasLykhenko <18290033+TarasLykhenko@users.noreply.github.com>
Signed-off-by: TarasLykhenko <18290033+TarasLykhenko@users.noreply.github.com>
@EItanya

EItanya commented Nov 7, 2026

Copy link
Copy Markdown

Will be closed by #148

@EItanya EItanya closed this Nov 7, 2026
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