docs: note Kibana 7→8 migration known issue on 3.21 and 3.22 release notes#2729
docs: note Kibana 7→8 migration known issue on 3.21 and 3.22 release notes#2729tianfeng92 wants to merge 1 commit into
Conversation
✅ Deploy Preview for calico-docs-preview-next ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview succeeded!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
@tianfeng92 Can you provide more information about this? This seems ultimately to be a bug fix statement, so I'm not sure why we need to add a special admonition. |
@ctauchen The admonition is intentional because this is an upgrade-path hazard, not a typical runtime bug. Users upgrading from 3.20 or earlier will hit a Kibana crashloop during the saved-object migration — by the time they see it, they're already stuck in a broken state. The note is placed at the top of the release section so it's visible before someone starts the upgrade, rather than buried in the bug-fix list where it reads like a post-facto fix. Once 3.21.8 / 3.22.5 ship with the fix included, we can remove the admonition and leave just the bug-fix line item. |
|
|
tianfeng92
force-pushed
the
kibana-7-8-migration-known-issue
branch
from
9984c85 to
f4af653
Compare
…notes Add upgrade notes on the 3.21.7, 3.22.3, and 3.22.4 release sections warning about the known Kibana 7→8 saved-object migration issue when upgrading from Calico Enterprise 3.20 or earlier. The fix shipped in 3.21.8 and 3.22.5. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
tianfeng92
force-pushed
the
kibana-7-8-migration-known-issue
branch
from
f4af653 to
6a57482
Compare
4 participants
Summary
Test plan
🤖 Generated with Claude Code