Fix enableImpersonation flag type consistency #245
Merged
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.
Summary
Fix type inconsistency for enableImpersonation configuration across cluster-proxy components and add validation to prevent invalid values.
enableImpersonationfrom string"true"to booleantruein addon-agent values.yamlChanges Made
1. Type Consistency Fix
2. Input Validation (New)
"true","false","1","0"(as defined by Go's flag.BoolVar)3. Feature Integration
Problem This Solves
Without validation, if a user sets
enableImpersonation: "fase"(typo):{{- if .Values.enableImpersonation }}evaluates totrue(non-empty string)invalid boolean value "fase" for -enable-impersonation: parse errorWith validation:
invalid value for enableImpersonation: "fase", must be one of: true, false, 1, 0Type Safety Details
The CRD
AdditionalValuesusesmap[string]string, but boolean defaults in values.yaml are semantically correct. Helm properly converts and evaluates these values at deployment time.Testing
All existing tests pass:
🤖 Generated with Claude Code