OTA(Over-The-Air) Upgrades For Edge Node#5863
OTA(Over-The-Air) Upgrades For Edge Node#5863kubeedge-bot merged 2 commits intokubeedge:masterfrom Believeht029:master
Conversation
wbc6080
left a comment
There was a problem hiding this comment.
Please make the verify CI check pass. You can refer to https://kubeedge.io/docs/developer/make_verify
cloud/pkg/taskmanager/nodeupgradecontroller/node_upgrade_controller.go
Outdated
Show resolved
Hide resolved
|
I have run |
wbc6080
left a comment
There was a problem hiding this comment.
Please squash some commits https://kubeedge.io/docs/developer/Supplemental_developer_guide#ensuring-to-squash-similiar-commits
fisherxu
left a comment
There was a problem hiding this comment.
Is the PR ready for review? Since it still has the WIP label :) @HT0403 @WillardHu
Signed-off-by: HT0403 <ht000229@qq.com>
|
This PR is ready for review, I remove the |
Signed-off-by: HT0403 <ht000229@qq.com>
fisherxu
left a comment
There was a problem hiding this comment.
/approve
Looks good for the first version!
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: fisherxu The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/lgtm |


What type of PR is this?
/kind feature
What this PR does / why we need it:
In order to make the edge node more convenient and rapid upgrade, we introduce a remote upgrade scheme OTA (Over-The-Air) into KubeEdge. In the main process of OTA(i.e. make the bundle, download the bundle, verify the bundle and firmware upgrade), we have realized most steps. Our release will generate a new image version called installation-package, then we use the NodeUpgradeJob CRD to obtain the installation tool keadm in the image and run the command to upgrade the edge node. During this process, if the hacker masquerades the image in the edge node, this will result in the untrusted binary keadm. We need to verify the digest of the image before the keadm executes the upgrade, which is the third step of OTA to verify the bundle. And in some business scenarios (Internet of vehicles, Internet of Things), we also need to provide an option to make the node wait for confirmation from a person with permission before upgrading the edge node.
Which issue(s) this PR fixes:
Fixes #5589
Special notes for your reviewer:
Does this PR introduce a user-facing change?: