Add blog post for KubeEdge deployment and validation on VisionFive2#787
Add blog post for KubeEdge deployment and validation on VisionFive2#787ddc-baiye wants to merge 2 commits into
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
kubeedge-bot
added
the
size/L
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request adds a new author and a detailed blog post documenting the validation of KubeEdge on the VisionFive2 RISC-V platform. The feedback identifies several issues in the provided shell commands and YAML manifests, including insecure download practices, missing sudo permissions for configuration edits, and the use of a container image that lacks RISC-V architecture support.
| sudo mkdir -p /etc/containerd | ||
| containerd config default | sudo tee /etc/containerd/config.toml | ||
|
|
||
| sed -i 's/SystemdCgroup = false/SystemdCgroup = true/' /etc/containerd/config.toml |
There was a problem hiding this comment.
The sed command is missing sudo. Since /etc/containerd/config.toml is typically owned by root, this command will fail with a "Permission denied" error.
sudo sed -i 's/SystemdCgroup = false/SystemdCgroup = true/' /etc/containerd/config.toml
There was a problem hiding this comment.
this it true, we need to add sudo or root user is required to issue this command.
There was a problem hiding this comment.
Updated. I added sudo to that command since root permission is required there. Thanks.
| containerd config default | sudo tee /etc/containerd/config.toml | ||
|
|
||
| sed -i 's/SystemdCgroup = false/SystemdCgroup = true/' /etc/containerd/config.toml | ||
| sed -i "s#registry.k8s.io/pause:3.10.1#registry.k8s.io/pause:3.9#g" /etc/containerd/config.toml |
There was a problem hiding this comment.
This sed command is missing sudo and relies on a specific version string (3.10.1) that may not match the default configuration of containerd v2.2.2. If the match fails, the pause image won't be updated to your locally built version, causing the edge node to fail when pulling the default image. Using a more generic pattern to match the sandbox_image key is more robust.
sudo sed -i 's#sandbox_image = ".*"#sandbox_image = "registry.k8s.io/pause:3.9"#' /etc/containerd/config.toml
| automountServiceAccountToken: false | ||
| containers: | ||
| - name: nginx-edge | ||
| image: nginx |
There was a problem hiding this comment.
The official nginx image does not currently support the riscv64 architecture. Readers following this tutorial will encounter errors when the edge node attempts to pull the image. Using a community-maintained RISC-V image like riscv64/nginx ensures the workload can run on the VisionFive2 board.
image: riscv64/nginx
ddc-baiye
force-pushed
the
blog/visionfive2-riscv-validation
branch
2 times, most recently
from
0abba61 to
ffefc93
Compare
| sudo mkdir -p /etc/containerd | ||
| containerd config default | sudo tee /etc/containerd/config.toml | ||
|
|
||
| sed -i 's/SystemdCgroup = false/SystemdCgroup = true/' /etc/containerd/config.toml |
There was a problem hiding this comment.
this it true, we need to add sudo or root user is required to issue this command.
Add the VisionFive2 RISC-V deployment and validation blog post. Also includes the author file newline fix and the runtime setup review updates. Signed-off-by: ddc-baiye <dongdong.chen@bluedotai.cn>
ddc-baiye
force-pushed
the
blog/visionfive2-riscv-validation
branch
from
c10c0b9 to
bb7afed
Compare
|
Thanks for the review. I have addressed the comments, squashed the commits into a single commit, and added the DCO sign-off. The branch has been force-pushed. Please take another look when you have time. |
3 participants
Summary
This PR adds a new blog post about deploying and validating KubeEdge on VisionFive2, a real RISC-V board.
The post shares a hands-on deployment and validation process covering dependency preparation, native build of KubeEdge components, edge node join, and basic workload deployment on riscv64.
Changes
blog/kubeedge-riscv-validation/blog/authors.ymlwith author informationNotes
This post focuses on validating the basic deployment path on VisionFive2 rather than full production readiness.