-
Notifications
You must be signed in to change notification settings - Fork 102
ROB-1413 CVE #504
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
ROB-1413 CVE #504
Conversation
WalkthroughThe changes update the Dockerfile to use newer kube-lineage binaries from a different GitHub organization and address a security issue by removing a specific setuptools wheel file. Additionally, the Changes
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
🧹 Nitpick comments (1)
Dockerfile (1)
135-135
: Improve setuptools removal to handle future versions.Hardcoding the exact wheel name may break when the base image bundles a different setuptools version. Use a wildcard to remove any bundled wheel:
-RUN rm -rf /usr/local/lib/python3.11/ensurepip/_bundled/setuptools-65.5.0-py3-none-any.whl +RUN rm -rf /usr/local/lib/python3.11/ensurepip/_bundled/setuptools-*.whl
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
⛔ Files ignored due to path filters (1)
poetry.lock
is excluded by!**/*.lock
📒 Files selected for processing (2)
Dockerfile
(2 hunks)pyproject.toml
(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (3)
- GitHub Check: Pre-commit checks
- GitHub Check: build (3.12)
- GitHub Check: Pre-commit checks
🔇 Additional comments (2)
pyproject.toml (2)
34-34
: Ensure lock file is updated and aligned with dependency bump.You’ve upgraded
setuptools
to^80.9.0
. Please confirm thatpoetry.lock
has been regenerated and committed so the new version is locked in CI/CD.
38-38
: Verify compatibility ofmarkdownify
major version upgrade.Bumping from
0.x
to1.x
can introduce breaking changes. Ensure existing code paths usingmarkdownify
still work and add or update tests for any altered behavior.
ARG KUBE_LINEAGE_ARM_URL=https://github.com/robusta-dev/kube-lineage/releases/download/v2.2.3/kube-lineage-macos-latest-v2.2.3 | ||
ARG KUBE_LINEAGE_AMD_URL=https://github.com/robusta-dev/kube-lineage/releases/download/v2.2.3/kube-lineage-ubuntu-latest-v2.2.3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Verify ARM binary URL correctness.
The ARM download URL points to a macos
asset (kube-lineage-macos-latest-v2.2.3
) under a Linux/ARM64 platform check. Confirm the GitHub release actually provides that file or update this to the correct linux-arm64
binary.
🤖 Prompt for AI Agents
In the Dockerfile at lines 29-30, the ARM binary URL points to a macOS asset
instead of a Linux ARM64 binary. Verify the GitHub release assets to find the
correct Linux ARM64 binary URL and update the KUBE_LINEAGE_ARM_URL argument
accordingly to ensure the correct binary is downloaded for ARM64 Linux
platforms.
No description provided.