Optimization of kubeedge deployment documentation: Handling issues with insufficient edge node resources for normal deployment. #551
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.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Welcome @hyp4293! It looks like this is your first PR to kubeedge/website 🎉 |
kubeedge-bot
added
the
size/M
Signed-off-by: hyp4293 <[email protected]>
| In the case of insufficient qualifications for edge nodes, we need to label them to prevent some applications from extending to edge nodes. | ||
|
|
||
| ``` | ||
| kubectl get daemonset -n kube-system |grep -v NAME |awk '{print $1}' | xargs -n 1 kubectl patch daemonset -n kube-system --type='json' -p='[{"op": "replace","path": "/spec/template/spec/affinity","value":{"nodeAffinity":{"requiredDuringSchedulingIgnoredDuringExecution":{"nodeSelectorTerms":[{"matchExpressions":[{"key":"node-role.kubernetes.io/edge","operator":"DoesNotExist"}]}]}}}}]' |
There was a problem hiding this comment.
https://github.com/kubeedge/website/pull/551/files#diff-58f39633768f7241615b445ab20cf0842acb0f0f38597ca61e8c4afceeeac56fR308 has a similar description, we need to let users know that kube-proxy and some others is not required at the edge
There was a problem hiding this comment.
We will remind users that kube-proxy and some other components are not required at the edge. They can handle it accordingly.
docs/setup/install-with-keadm.md
Outdated
|
|
||
| ``` | ||
|
|
||
| Any daemonset cannot occupy the hardware resources of edge nodes. |
There was a problem hiding this comment.
I think this is too radical.
There was a problem hiding this comment.
This description is indeed too abrupt; we will make modifications.
We will use English in PR title and description |
…th insufficient edge node resources for normal deployment.
kubeedge-bot
added
size/S
hyp4293
changed the title
kubeedge-bot
added
size/L
|
Plz use English in commit message, thanks. |
| @@ -0,0 +1,156 @@ | |||
| # KubeEdge 镜像预加载功能指导文档 | |||
There was a problem hiding this comment.
Please push a separate PR to add imapePrepull guide. And it belongs to docs but not blog. A English version is also needed.
There was a problem hiding this comment.
We have resubmitted as requested
|
|
kubeedge-bot
added
the
needs-rebase
|
@hyp4293: PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Signed-off-by: GitHub <[email protected]> Signed-off-by: hyp4293 <[email protected]>
Signed-off-by: GitHub <[email protected]> Signed-off-by: hyp4293 <[email protected]>
Signed-off-by: GitHub <[email protected]> Signed-off-by: hyp4293 <[email protected]>
Signed-off-by: GitHub <[email protected]> Signed-off-by: hyp4293 <[email protected]>
Signed-off-by: GitHub <[email protected]> Signed-off-by: hyp4293 <[email protected]>
Signed-off-by: fisherxu <[email protected]> Signed-off-by: hyp4293 <[email protected]>
Signed-off-by: hyp4293 <[email protected]>
…th insufficient edge node resources for normal deployment. Signed-off-by: hyp4293 <[email protected]>
Signed-off-by: hyp4293 <[email protected]>
Signed-off-by: GitHub <[email protected]> Signed-off-by: hyp4293 <[email protected]>
Signed-off-by: hyp4293 <[email protected]>
Signed-off-by: hyp4293 <[email protected]>
Signed-off-by: hyp4293 <[email protected]>
Signed-off-by: wbc6080 <[email protected]> Signed-off-by: hyp4293 <[email protected]>
Signed-off-by: wbc6080 <[email protected]> Signed-off-by: hyp4293 <[email protected]>
Signed-off-by: Shubham Singh <[email protected]> Signed-off-by: hyp4293 <[email protected]>
kubeedge-bot
added
size/XL
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...
docs update,
What is the current behavior? (You can also link to an open issue here)
Optimization of kubeedge deployment documentation: Handling issues with insufficient edge node resources for normal deployment. By applying appropriate labels, prevent certain applications from extending to edge nodes, thereby conserving edge node resources and alleviating resource pressure on the nodes.
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
Other information: