Adding ability to set the dns policy and config for the runner pod#2061
Adding ability to set the dns policy and config for the runner pod#2061andrewgkew wants to merge 3 commits intorobusta-dev:masterfrom
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 (2)
🚧 Files skipped from review as they are similar to previous changes (1)
WalkthroughThe Helm chart adds a new Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~15 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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. Review rate limit: 7/8 reviews remaining, refill in 7 minutes and 30 seconds.Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@helm/robusta/templates/runner.yaml`:
- Around line 45-58: The dnsConfig block is being emitted at the wrong YAML
level: when .Values.runner.dnsConfig.enabled is true, ensure you output a
top-level dnsConfig: mapping and nest dnsPolicy, nameservers, searches, and
options under it; update the template in runner.yaml to render a single
dnsConfig: key (using .Values.runner.dnsConfig) and then conditionally render
dnsPolicy and the three child lists (nameservers, searches, options) indented
under dnsConfig so the Kubernetes Pod spec is valid.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: b1d3a11c-1d53-46db-8820-11c1eaef623e
📒 Files selected for processing (2)
helm/robusta/templates/runner.yamlhelm/robusta/values.yaml
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@helm/robusta/templates/runner.yaml`:
- Around line 47-59: The template emits a bare `dnsConfig:` key when all
sub-lists are empty; wrap the entire dnsConfig block with a guard that checks
whether any of .Values.runner.dnsConfig.nameservers,
.Values.runner.dnsConfig.searches, or .Values.runner.dnsConfig.options are
non-empty (use an {{- if or ... }} / {{- end }} around the dnsConfig: stanza) so
dnsConfig is omitted entirely when all three are empty; reference the existing
dnsConfig:, .Values.runner.dnsConfig.nameservers,
.Values.runner.dnsConfig.searches, and .Values.runner.dnsConfig.options symbols
when implementing the guard.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: aea6b190-1f80-4075-ad73-f643cc4939d2
📒 Files selected for processing (1)
helm/robusta/templates/runner.yaml
…so added checks so if policy is None one of the configs are set
Currently the helm chart is missing the capability to set the DNS Policy and DNS Config of the runner pod
Adding this ability. By default its turned off and defaults to ClusterFirst which is the default value for this field if this doesnt exist