-
Notifications
You must be signed in to change notification settings - Fork 157
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Optimization of kubeedge deployment documentation: Handling issues with insufficient edge node resources for normal deployment. #551
Open
hyp4293
wants to merge
22
commits into
kubeedge:master
Choose a base branch
from
hyp4293:master
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from 1 commit
Commits
Show all changes
22 commits
Select commit
Hold shift + click to select a range
c96e24a
kubeedge部署文档内容优化:边缘节点资源紧张无法正常部署的问题处理
hyp4293 571e55c
Optimization of kubeedge deployment documentation: Handling issues wi…
hyp4293 a294732
镜像预加载功能指导文档
hyp4293 b2f2d09
Merge remote-tracking branch 'upstream/master'
hyp4293 d75689d
New Blog for Release KubeEdge v1.11
1Shubham7 214001a
fixed the release date
1Shubham7 b512169
New Blog for Release KubeEdge v1.11
1Shubham7 cd9db44
New Blog for Release KubeEdge v1.14
1Shubham7 755bcee
added the release date
1Shubham7 11c7d68
update version for release 1.17
fisherxu 18d7615
kubeedge部署文档内容优化:边缘节点资源紧张无法正常部署的问题处理
hyp4293 345a540
Optimization of kubeedge deployment documentation: Handling issues wi…
hyp4293 4af8dd1
镜像预加载功能指导文档
hyp4293 1712f6a
Replacing Twitter with X
1Shubham7 603928a
Merge branch 'master' of https://github.com/hyp4293/website
hyp4293 d59f6bc
KubeEdge Image PrePull Feature Guide Document
hyp4293 52ac1e3
KubeEdge Image PrePull Feature Guide Document
hyp4293 bf2a75e
6/7/2024
hyp4293 3bb5a84
add case study about raisecom tech
wbc6080 0c2e057
add case study about XingHai IoT
wbc6080 a5f98d9
Part 1: improving the install with keadm docs
1Shubham7 628e9d7
fix merge
hyp4293 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -97,6 +97,23 @@ keadm init --set server.advertiseAddress="THE-EXPOSED-IP" --set server.nodeName= | |
If you are familiar with the helm chart installation, please refer to [KubeEdge Helm Charts](https://github.com/kubeedge/kubeedge/tree/master/manifests/charts). | ||
|
||
|
||
**SPECIAL SCENARIO:** | ||
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"}]}]}}}}]' | ||
|
||
``` | ||
|
||
|
||
``` | ||
kubectl get daemonset -n metallb-system |grep -v NAME |awk '{print $1}' | xargs -n 1 kubectl patch daemonset -n metallb-system --type='json' -p='[{"op": "replace","path": "/spec/template/spec/affinity","value":{"nodeAffinity":{"requiredDuringSchedulingIgnoredDuringExecution":{"nodeSelectorTerms":[{"matchExpressions":[{"key":"node-role.kubernetes.io/edge","operator":"DoesNotExist"}]}]}}}}]' | ||
hyp4293 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
``` | ||
|
||
Any daemonset cannot occupy the hardware resources of edge nodes. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think this is too radical. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This description is indeed too abrupt; we will make modifications. |
||
|
||
|
||
### keadm manifest generate | ||
|
||
You can also get the manifests with `keadm manifest generate`. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We will remind users that kube-proxy and some other components are not required at the edge. They can handle it accordingly.