State that upgrading rpk does not upgrade the AI plugin - #191
Open
JakeSCahill wants to merge 1 commit into
Open
Conversation
Verified empirically (DOC-2417): a plugin pinned at 0.2.30 survived an rpk 26.1.12 to 26.2.1 upgrade untouched, across invocations, and moved only on rpk ai upgrade. Also ties the reference's introduced-in notes to the plugin version so readers on stale plugins know why a documented command is missing.
✅ Deploy Preview for redpanda-agentic-data-plane ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
micheleRP
approved these changes
Aug 5, 2026
micheleRP
left a comment
micheleRP
left a comment
Contributor
There was a problem hiding this comment.
Reviewed against docs-team-standards. No critical issues — this is a clean, well-tested two-line fix (DOC-2417), backed by a reproducible empirical test in the Jira ticket.
A couple of suggestions worth considering, not blocking:
modules/gateway/pages/connect-agent.adoc(lines 51-58) has a near-duplicaterpk ai install/upgrade/uninstallwalkthrough under "Userpk aifor local development" that doesn't get the same NOTE. DOC-2417 calls out "the plugin install pages" (plural) — consider adding the same note (or a link back to this page) there too.- Once redpanda-data/docs#1883 merges, consider linking to its new "Upgrade rpk plugins" section via
xref:reference:rpk-install.adoc[](already linked earlier on this page) so this NOTE points to the general explanation instead of only restating therpk ai-specific case.
Approving as-is — these are follow-ups, not blockers.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Adds a NOTE to the CLI install section: the plugin is a separate binary that survives
rpkupgrades untouched untilrpk ai upgraderuns — empirically verified (a plugin pinned at 0.2.30 survived an rpk v26.1.12 → v26.2.1 upgrade across invocations, and moved to 0.2.34 only on explicit upgrade; test log and repro in the Jira). Also connects the reference's "introduced in ai version X" notes to the plugin version, so a reader whose documented command is missing knows the fix is one upgrade away.Companion to redpanda-data/docs#1883 and rp-connect-docs#479.
Jira
Part of DOC-2417.