Skip to content

docs: update Troubleshooting guide for v1.21 with final cleanup#730

Open
sachin21212121 wants to merge 2 commits intokubeedge:masterfrom
sachin21212121:docs/troubleshooting-md
Open

docs: update Troubleshooting guide for v1.21 with final cleanup#730
sachin21212121 wants to merge 2 commits intokubeedge:masterfrom
sachin21212121:docs/troubleshooting-md

Conversation

@sachin21212121
Copy link

Update KubeEdge Troubleshooting guide with fixes for keadm init, CRDs for v1.21.0, pod troubleshooting, logging instructions, and formatting improvements from #726 (#726).

Signed-off-by: sachin21212121 <jhasachin0115@gmail.com>
@kubeedge-bot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign fisherxu after the PR has been reviewed.
You can assign the PR to them by writing /assign @fisherxu in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@gemini-code-assist
Copy link

Summary of Changes

Hello @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 focuses on refining the KubeEdge Troubleshooting guide to align with version 1.21.0. The updates provide more accurate and user-friendly instructions for common issues such as keadm init failures due to connectivity, problems with container lifecycle states, and methods for retrieving various logs. The changes aim to enhance the overall documentation quality and improve the troubleshooting experience for KubeEdge users.

Highlights

  • Updated keadm init Troubleshooting: The guide for keadm init failures has been comprehensively updated for KubeEdge v1.21.0, including specific instructions for manually downloading release packages and using the correct v1beta1 CRDs.
  • Enhanced Container Lifecycle Troubleshooting: The section addressing 'Container keeps Pending or Terminating' issues has been rephrased for improved clarity and readability, providing a more structured troubleshooting flow.
  • Improved Logging Instructions: Instructions for viewing CloudCore, EdgeCore, and pod logs have been consolidated and expanded, now including journalctl commands for cloudcore.service and guidance on enabling remote kubectl logs access.
  • New 'Important Considerations' Section: A new section has been added to highlight crucial information regarding CRD versions (specifically v1beta1 for devices since v1.15), the importance of version number replacement, and the location of official release artifacts.
Using Gemini Code Assist

The 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 /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

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 .gemini/ folder in the base of the repository. Detailed instructions can be found here.

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

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@kubeedge-bot kubeedge-bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Sep 26, 2025
Copy link

@gemini-code-assist gemini-code-assist bot left a 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 significantly improves the troubleshooting documentation by updating it for KubeEdge v1.21, reorganizing the content for better clarity, and enhancing the formatting. The guide is now much more user-friendly and informative. I have a couple of minor suggestions to fix some formatting issues in the markdown.

│ ├── cluster_objectsync_v1alpha1.yaml
│ └── objectsync_v1alpha1.yaml
└── kubeedge-v1.21.0-linux-amd64.tar.gz
````

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

There's a typo in the closing fence of this code block. It uses four backticks (````) instead of the standard three (```). This should be corrected to ensure the markdown renders correctly across all platforms.

Suggested change
````

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this needs to be addressed.

Comment on lines 130 to 133
<!-- end list -->

You can also enable `kubectl logs` feature refer to this [guide](../advanced/debug.md). No newline at end of file
```
```

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

These trailing lines appear to be leftover artifacts and should be removed. The HTML comment <!-- end list --> serves no purpose here, and the empty code blocks will render as empty boxes, which is likely not intended. Removing them will provide a cleaner end to the document.

Copy link
Contributor

@fujitatomoya fujitatomoya left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sachin21212121 out of curiosity, did you try to build the doc site in local env?

│ ├── cluster_objectsync_v1alpha1.yaml
│ └── objectsync_v1alpha1.yaml
└── kubeedge-v1.21.0-linux-amd64.tar.gz
````
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this needs to be addressed.

Comment on lines +132 to +133
```
```
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why do we even need this code block?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fujitatomoya you're right i will remove this

@fujitatomoya
Copy link
Contributor

@sachin21212121 are you still working on this?

@sachin21212121
Copy link
Author

fujitatomoya

yes, i was occupied with some work, but now i am happy to contribute further

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants