-
Notifications
You must be signed in to change notification settings - Fork 176
docs: update install-with-keadm.md for KubeEdge v1.21 with corrected links and metrics-server YAML #733
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
base: master
Are you sure you want to change the base?
docs: update install-with-keadm.md for KubeEdge v1.21 with corrected links and metrics-server YAML #733
Conversation
…links and metrics-server YAML Signed-off-by: sachin21212121 <[email protected]>
…1.21 Signed-off-by: sachin21212121 <[email protected]>
…links and metrics-server YAML Signed-off-by: sachin21212121 <[email protected]>
|
[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 |
Summary of ChangesHello @sachin21212121, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request significantly refines the Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
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.
Code Review
This pull request provides a significant and valuable update to the install-with-keadm.md documentation, bringing it up to date for KubeEdge v1.21. The refactoring has greatly improved readability and conciseness by removing outdated information, fixing links, and reorganizing content. My review focuses on further enhancing clarity and preventing potential user errors, particularly in the metrics-server setup instructions. I've identified a couple of high-severity issues related to a hardcoded node name and an undefined environment variable that could cause commands to fail for users. Additionally, I've suggested some medium-severity improvements for consistency in markdown formatting and command examples.
| ```shell | ||
| keadm deprecated join --cloudcore-ipport="THE-EXPOSED-IP":10000 --token=27a37ef16159f7d3be8fae95d588b79b3adaaf92727b72659eb89758c66ffda2.eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJleHAiOjE1OTAyMTYwNzd9.JBj8LLYWXwbbvHKffJBpPd5CyxqapRQYDIXtFZErgYE --kubeedge-version=1.12.0 | ||
| ```bash | ||
| iptables -t nat -A OUTPUT -p tcp --dport 10350 -j DNAT --to $CLOUDCOREIPS:10003 |
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.
The command uses the environment variable $CLOUDCOREIPS, but this variable is not defined or mentioned in this document. This will cause the command to fail for users. Please add a note before this code block explaining that $CLOUDCOREIPS should be set to the IP address of the CloudCore instance. For example: export CLOUDCOREIPS="<your-cloudcore-ip>".
| - key: kubernetes.io/hostname | ||
| operator: In | ||
| values: | ||
| - charlie-latest |
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.
The value charlie-latest is a hardcoded node name. This will cause the deployment to fail for users who don't have a node with this exact name. Please replace it with a placeholder like <your-master-node-name> and add a comment explaining that users need to replace it with their actual master node's hostname.
| - charlie-latest | |
| - <your-master-node-name> |
| 3. Build from Source | ||
|
|
||
| - Refer to [build from source](./install-with-binary#build-from-source) for instructions. | ||
| ### 2\. Download from Docker Hub |
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.
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.
i second this suggested change.
| ``` | ||
|
|
||
| By default, ports `10000` and `10002` on your CloudCore needs to be accessible for your edge nodes. | ||
| ### 3\. Build from Source |
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.
|
|
||
| You can also use `keadm deprecated join` to start EdgeCore from the release package. It will download release packages from [KubeEdge release website](https://github.com/kubeedge/kubeedge/releases), and then start `edgecore` in binary progress. | ||
| ```bash | ||
| kubectl apply -f <deployment-yaml> |
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.
The placeholder <deployment-yaml> is a bit vague. Since an example with a filename is provided just below (metrics-server-deployment.yaml), it would be more helpful and direct for the user to use that filename in the command.
| kubectl apply -f <deployment-yaml> | |
| kubectl apply -f metrics-server-deployment.yaml |
fujitatomoya
left a comment
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.
i got several comments for this PR, most of them are cosmetic fixes.
| ```shell | ||
| docker run --rm kubeedge/installation-package:v1.17.0 cat /usr/local/bin/keadm > /usr/local/bin/keadm && chmod +x /usr/local/bin/keadm | ||
| ``` | ||
| ```bash |
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.
i do not see the hard requirement to be bash in this code block? and there are many places that use shell as well, why this needs to be bash prompt?
| 3. Build from Source | ||
|
|
||
| - Refer to [build from source](./install-with-binary#build-from-source) for instructions. | ||
| ### 2\. Download from Docker Hub |
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.
i second this suggested change.
| Keadm is used to install the cloud and edge components of KubeEdge. | ||
| It does **not** handle Kubernetes installation or its [runtime environment](https://kubeedge.io/docs/setup/prerequisites/runtime). | ||
| Check [Kubernetes compatibility](https://github.com/kubeedge/kubeedge?tab=readme-ov-file#kubernetes-compatibility) to confirm supported versions. |
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.
if we are trying to recommend or enforce the rule that single sentence per line, this does not really work for us unless we have some static checker to detect the PR via github workflow? i mean, we can fix one by one, but this goes out of control anyway, because there is no systematic check.
This PR updates the install-with-keadm.md documentation for KubeEdge v1.21. Key changes include: