Skip to content

Update KubeVirt CSI Driver - #409

Merged
Andrei Kvapil (kvaps) merged 1 commit into
mainfrom
upd-csi-driver
Oct 9, 2024
Merged

Update KubeVirt CSI Driver#409
Andrei Kvapil (kvaps) merged 1 commit into
mainfrom
upd-csi-driver

Conversation

@kvaps

@kvaps Andrei Kvapil (kvaps) commented Oct 9, 2024 •
edited by coderabbitai Bot
Loading

Copy link
Copy Markdown
Member

Signed-off-by: Andrei Kvapil kvapss@gmail.com

Summary by CodeRabbit

  • Chores
    • Updated the build stage of the KubeVirt CSI Driver to use a newer commit hash for improved stability and features.

@kvaps
Update KubeVirt CSI Driver
b862ff2 
Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
@coderabbitai

coderabbitai Bot commented Oct 9, 2024 •
edited
Loading

Copy link
Copy Markdown
Contributor

Caution

Review failed

The pull request is closed.

Walkthrough

The changes involve an update to the Dockerfile for the KubeVirt CSI Driver, specifically in the build stage. The git checkout command has been modified to switch from one commit hash to a newer commit hash, indicating a change in the source code version being utilized for the build process. No other modifications were made to the Dockerfile.

Changes

File Path Change Summary
packages/apps/kubernetes/images/kubevirt-csi-driver/Dockerfile Updated git checkout command to switch to a newer commit hash (from fa92820448e583c7fd722dc20270544e0c3eca53 to 35836e0c8b68d9916d29a838ea60cdd3fc6199cf).

Sequence Diagram(s)

sequenceDiagram
    participant Builder as Docker Builder
    participant Repo as Git Repository
    Builder->>Repo: git checkout 35836e0c8b68d9916d29a838ea60cdd3fc6199cf
    Repo-->>Builder: Checkout new commit
Loading

Poem

In the land of code where rabbits play,
A Dockerfile changed in a splendid way.
A new commit found, a hop and a skip,
To build the driver, we take a new trip!
With each little change, our project will grow,
Hopping along with the code's gentle flow! 🐇✨

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@kvaps
Andrei Kvapil (kvaps) merged commit 4631ea2 into main Oct 9, 2024
@kvaps
Andrei Kvapil (kvaps) deleted the upd-csi-driver branch October 9, 2024 15:49
chumkaska pushed a commit to chumkaska/cozystack that referenced this pull request Oct 15, 2024
@kvaps @agaenix
Update KubeVirt CSI Driver (cozystack#409)
17adb68 
Signed-off-by: Andrei Kvapil <kvapss@gmail.com>

Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
@coderabbitai coderabbitai Bot mentioned this pull request Jun 30, 2025
Merged
@coderabbitai coderabbitai Bot mentioned this pull request Jul 8, 2025
Merged
Aleksei Sviridkin (lexfrei) added a commit that referenced this pull request Mar 23, 2026
@lexfrei
[kilo] Switch from fork to upstream squat/kilo
b43b7b2 
All functional patches from the cozystack/kilo fork have been
upstreamed and included in squat/kilo v0.7.0:
- --internal-cidr flag (PR #403)
- allowed-location-ips overlap fix (PR #404)
- Auto-detect WireGuard MTU (PR #406)
- Preferred source for WireGuard routes (PR #408)
- Cilium IPIP overlay support (PR #409)

The fork only contained rebranding and CI-specific commits beyond
upstream, which are no longer needed.

Assisted-By: Claude <noreply@anthropic.com>
Signed-off-by: Aleksei Sviridkin <f@lex.la>
@lexfrei Aleksei Sviridkin (lexfrei) mentioned this pull request Mar 23, 2026
Merged
Kirill Ilin (sircthulhu) added a commit that referenced this pull request Mar 26, 2026
@sircthulhu
[kilo] Switch from fork to upstream squat/kilo (#2259)
f13e68a 
## What this PR does

Switch kilo from the cozystack/kilo fork to the upstream squat/kilo
repository (v0.7.0).

All functional patches from the fork have been upstreamed:
- `--internal-cidr` flag for IP auto-detection filtering (#403)
- Allowed-location-ips overlap with node IPs fix (#404)
- Auto-detect WireGuard MTU from underlay interface (#406)
- Preferred source for WireGuard routes (#408)
- Cilium IPIP overlay support (#409)

The fork only retained rebranding and CI-specific commits beyond
upstream, which are no longer needed.

Changes:
- Makefile: point to `squat/kilo` repo and `ghcr.io/squat/kilo` image
- values.yaml: updated via `make update` to `0.7.0` with digest pin

### Release note

```release-note
[kilo] Switch from cozystack/kilo fork to upstream squat/kilo v0.7.0
```


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Updates**
* Updated the kilo component to use a different source repository and
new version configuration.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@kvaps