Proposal: support edge nodes report events#5722
Conversation
|
Welcome @llmmqq8023! It looks like this is your first PR to kubeedge/kubeedge 🎉 |
kubeedge-bot
added
the
size/L
Shelley-BaoYue
left a comment
Shelley-BaoYue
left a comment
There was a problem hiding this comment.
Looks good to me : )
Please add a head at the top of proposal file, format like:
---
title: xxx
authors:
- "@xxx"
approvers:
creation-date: 2024-07-12
last-updated: 2024-07-12
status: implementable
---
llmmqq8023
force-pushed
the
support-edge-nodes-report-events-proposal
branch
from
ea70afa to
6ea1674
Compare
|
/assign @daixiang0 |
Shelley-BaoYue
left a comment
Shelley-BaoYue
left a comment
There was a problem hiding this comment.
Commit name is used to let others to known what work has done in this commit. You can just squash these two commit to one, or name the second commit with add title for event report proposal
llmmqq8023
force-pushed
the
support-edge-nodes-report-events-proposal
branch
from
5f603cb to
cfb35c7
Compare
Signed-off-by: llmmqq8023 <273337875@qq.com> OK, I added a title. Signed-off-by: llmmqq8023 <273337875@qq.com> proposal for "supporting edge nodes report events" Signed-off-by: llmmqq8023 <273337875@qq.com>
llmmqq8023
force-pushed
the
support-edge-nodes-report-events-proposal
branch
from
cfb35c7 to
448f1e1
Compare
| 1. Pod Lifecycle Event Generator (PLEG), which is deployed in Kubelet, generates an event, and then the EventBridge API implemented in metaclient is called to report this event to the cloud. | ||
| 2. Metaclient wraps this event into beehive message and puts it into the specific beehive channel. | ||
| 3. Metamanager grabs the event message and give it to processEvent handler. | ||
| 4. The event is stored in the edge (optional). |
There was a problem hiding this comment.
@llmmqq8023 Maybe it's not necessary to store the message in metamanager, we don't need provide the option.
- Based on the functional responsibilities of edged, any module of EdgeD won't attempt to retrieve events.
- The loss of events doesn't significantly impact the overall system availability, meanwhile there are still log file retained.
fisherxu
left a comment
fisherxu
left a comment
There was a problem hiding this comment.
The config field SendEvent or ReportEvent should be added to the proposal :)
Signed-off-by: llmmqq8023 <273337875@qq.com>
|
[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 |
kubeedge-bot
added
the
approved
6 participants
What type of PR is this?
/kind design
What this PR does / why we need it:
Proposal: support edge nodes report events
issue: #5595