Fix setup-venv when hardened FS

[moshemorad]

No description provided.

[coderabbitai]

Walkthrough

Updated init container command in Helm template to set SRC to /venv/lib/python<major.minor>/site-packages instead of /venv/lib/<major.minor>/site-packages for copying site-packages into /venv-writable/. No other control flow or declarations changed.

Changes

Cohort / File(s)	Summary
Helm runner init path update helm/robusta/templates/runner.yaml	Adjust SRC path in init command from /venv/lib/<major.minor>/site-packages to /venv/lib/python<major.minor>/site-packages for site-packages copy step.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description Check	⚠️ Warning	No pull request description was provided, so there is no information describing the changes or their purpose, which fails to meet the minimal requirement for contextual clarity.	Please add a brief description summarizing the path adjustment in the init container command and the reason for fixing setup-venv under a hardened filesystem to provide reviewers with necessary context.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title Check	✅ Passed	The title succinctly captures the primary change by indicating that the setup of the virtual environment is fixed to support hardened filesystems, which directly reflects the modifications to the init container command path in runner.yaml.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch ROB-2260-support-read-only-file-system

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 53bd62c and 2d22b7a.

📒 Files selected for processing (1)

• helm/robusta/templates/runner.yaml (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: run_tests
• GitHub Check: run_tests

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}