fix(operator): preserve alpha service metadata precedence - #14855
Conversation
Signed-off-by: Julien Mancuso <jmancuso@nvidia.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review. WalkthroughThe DGD metadata propagation path now receives the full DGD. It preserves converted service metadata, filters conflicting graph metadata, and applies remaining graph values as defaults. Tests verify service and pod precedence. ChangesDGD metadata propagation
Priority: ⬇️ Low Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to The metadata precedence regression is covered by the added test, with no remaining actionable risk identified. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Comment |
Signed-off-by: Julien Mancuso <jmancuso@nvidia.com>
|
/ok to test 52ae45a |
Signed-off-by: Julien Mancuso <jmancuso@nvidia.com>
|
/ok to test fbc6168 |
Summary
Linear: https://linear.app/nvidia/issue/DYN-4442/dynamo150dgdr-service-level-specservicesnameannotationslabels-silently
Validation
GOCACHE=/private/tmp/dynamo-dyn4442-pr-go-cache go test ./internal/dynamo ./internal/dgdoverride ./api/v1alpha1 -count=1git diff --checkpre-commitwas not available in the local environment.Closes DYN-4442
Summary by CodeRabbit