fix: propagate Helm image pull secrets with native shapes - #148
Merged
Conversation
Greptile SummaryThe PR fixes image pull secret propagation across generated Kubernetes and Helm values.
Confidence Score: 5/5The PR appears safe to merge. No blocking failure remains; the previous scalar-typing issue is fixed across every image pull secret rendering path and covered by profile and discovery-daemon regression tests. Important Files Changed
Reviews (2): Last reviewed commit: "fix: quote rendered image pull secret na..." | Re-trigger Greptile |
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.
Summary
Root cause
The Network Operator chart wraps each root imagePullSecrets entry in a LocalObjectReference. l8k already rendered each entry as a name object, producing a nested value such as {name: {name: ngc-image-secret}}. Kubernetes then rejected the keep-ncp pre-install Job because spec.template.spec.imagePullSecrets[].name was an object instead of a string.
The subcharts do not share one schema: SR-IOV Operator expects secret-name strings, while NFD and Maintenance Operator expect LocalObjectReference objects. The generated values now preserve those chart-specific contracts.
All secret-name interpolations are quoted so valid Kubernetes names such as true, null, and 123 cannot be retyped by the YAML parser.
Testing