Skip to content

docs: update stale KubeEdge version references in keadm/keink setup guides - #866

Open
Priyanshubhartistm wants to merge 1 commit into
kubeedge:masterfrom
Priyanshubhartistm:fix-stale-keadm-keink-versions
Open

docs: update stale KubeEdge version references in keadm/keink setup guides#866
Priyanshubhartistm wants to merge 1 commit into
kubeedge:masterfrom
Priyanshubhartistm:fix-stale-keadm-keink-versions

Conversation

@Priyanshubhartistm

Copy link
Copy Markdown
  • Please check if the PR fulfills these requirements
  • The commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

Which issue(s) this PR fixes:
Fixes #

  • What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Docs fix.

  • What is the current behavior? (You can also link to an open issue here)

docs/setup/install-with-keadm.md mixes two different KubeEdge versions in the same document: the cloud-side install examples (wget/docker run/keadm init) use v1.17.0, while the edge-side keadm join examples use v1.12.1 / 1.12.0. Both are well behind the current release (v1.23.1), and having two different versions in one walkthrough is confusing for anyone copy-pasting the commands.

docs/setup/install-with-keink.md has a similar problem, but worse line 33 claims "Deploy the latest recommended version of KubeEdge v1.17", which is just false at this point and will go stale again the next time a release ships.

Same issues exist in the Chinese translations of both files.

  • What is the new behavior (if this is a feature change)?

install-with-keadm.md now uses v1.23.1 consistently across every example command (download, docker run, keadm init, keadm join, keadm deprecated join), in both English and Chinese.

install-with-keink.md no longer hardcodes a version number in prose it now links to the GitHub releases page instead, so the line doesn't need to be manually bumped on every release going forward. Same change applied to the Chinese translation.

Verified all four pages with yarn start (English and Chinese locales) and confirmed the rendered output shows the corrected versions/link. codespell --config codespell.cfg and yarn build both pass.

  • Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

No.

  • Other information:

Scoped this narrowly to the version strings themselves, not a rewrite of either guide a few earlier PRs (#721, #725, #730-733) attempted broader install-with-keadm.md updates for older releases and stalled/got auto-closed, so keeping this mechanical.

…uides

Signed-off-by: Priyanshubhartistm <bhartipriyanshustm@gmail.com>
@gemini-code-assist

Copy link
Copy Markdown

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.

@kubeedge-bot

Copy link
Copy Markdown
Collaborator

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign dingyin after the PR has been reviewed.
You can assign the PR to them by writing /assign @dingyin 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

@kubeedge-bot kubeedge-bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Aug 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants