fix wrong references with absolute URL links.#804
Conversation
Signed-off-by: Tomoya Fujita <tomoya.fujita825@gmail.com>
|
[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. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
kubeedge-bot
added
the
size/L
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request adds a new documentation guide for checking CloudCore logs and updates relative links to absolute URLs in the CNI edge networking documentation. The reviewer noted that the new CloudCore logs guide is written in English but placed under the Chinese translation directory, and should be translated to Chinese to maintain localization consistency.
| --- | ||
| title: Checking CloudCore Logs | ||
| sidebar_position: 12 | ||
| --- | ||
|
|
||
| > **Applies to:** KubeEdge v1.13+ | ||
| > **Related issue:** [kubeedge#6703](https://github.com/kubeedge/kubeedge/issues/6703) | ||
|
|
||
| When a KubeEdge installation fails or CloudCore behaves unexpectedly at runtime, inspecting CloudCore logs is the first and most effective diagnostic step. This guide explains **where logs are stored**, **which commands to run**, and **what log entries to look for** depending on how CloudCore is deployed. |
There was a problem hiding this comment.
This new documentation file is placed under the Chinese translation directory (i18n/zh/...), but the entire content is written in English. Please translate the document into Chinese to maintain localization consistency for Chinese readers.
| @@ -0,0 +1,354 @@ | |||
| --- | |||
There was a problem hiding this comment.
this is supposed to be Chinese but just to address the current build failure, i went ahead to copy the English one so that build succeeds.
|
@Shelley-BaoYue i think this one is high priority to fix the doc build failure, which affects the all the other PRs. |
2 participants
Which issue(s) this PR fixes:
Fixes #803
Just fixes the dead links and build failure.
zh doc build fails.
it does succeed.
No
this failure has been introduced by #794 and #802