fix: preserve kubernetes discovery env for worker command steps#1924
fix: preserve kubernetes discovery env for worker command steps#1924
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
📝 WalkthroughWalkthroughThe pull request adds Kubernetes in-cluster discovery environment variables to the list of allowed environment variable prefixes. Variables starting with Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 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 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1924 +/- ##
=======================================
Coverage 68.77% 68.78%
=======================================
Files 457 457
Lines 57637 57637
=======================================
+ Hits 39638 39643 +5
+ Misses 14388 14381 -7
- Partials 3611 3613 +2
... and 11 files with indirect coverage changes Continue to review full report in Codecov by Sentry.
🚀 New features to boost your workflow:
|
Summary
KUBERNETES_discovery env vars through the filtered base env used for step executionTesting
Related to #1922
Summary by CodeRabbit
KUBERNETES_(such as service host and port information) are now preserved and passed to child processes, enabling better Kubernetes in-cluster discovery support.