fix(helm): Add the missing max_concurrent_jobs config option for compression-coordinator in the values file. - #2495
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 4 included reviews per hour; 3 remain after this review. WalkthroughThe Helm chart version was incremented to ChangesHelm chart update
Estimated code review effort: 1 (Trivial) | ~5 minutes Merge Risk: ⚪ Minimal · up to This PR adds the missing Helm configuration for compression-coordinator without any identified merge-blocking risk; it is merge-ready after normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…r's config map section.
20001020ycx
left a comment
There was a problem hiding this comment.
I can confirm that the missing config is now propagated to the compression coordinator by spinning up the k8s cluster through kind.
Description
In #2435, we introduced a new config option named
max_concurrent_jobsforcompression-coordinator. However, the values file is not updated as a part of that PR. This PR fixes this issue by adding this missing option in the values file.Checklist
breaking change.
Validation performed
Summary by CodeRabbit
New Features
Chores