Repository navigation
twingate-connector: return log level to chart default - #198
Merged
Merged
Conversation
Debug logging was turned on for the connector's first deployment to diagnose the network-slug issue. The connector is stable now, so drop the logLevel override and use the chart default (error, level 3). Real-time connection logs (logAnalytics: v2) stay enabled. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Part of #184.
What
Remove
connector.logLevel: debugfromcomponents/value-overrides/twingate-connector-values.yaml, so the connector uses the chart default. Keepconnector.logAnalytics: v2(real-time connection logs).Debug logging was turned on for the connector's first deployment, to diagnose the network-slug issue (sedemo-infra-iac#22). The connector has been stable since, and debug output (STUN/relay maintenance and health checks every few seconds) is mostly noise.
Rendered change (chart 0.1.35)
3is the chart's fallback whenlogLevelis unset (error).Impact
Syncing
twingate-connectorchanges one env var on the Deployment, so the connector pod restarts once. Expect a few seconds of interruption for Twingate clients, includingkubectlaccess to the private EKS API.🤖 Generated with Claude Code