Skip to content

[release-v1.40] fix(kibana): discard unknown saved objects on upgrade from 7.x#4744

Merged
marvin-tigera merged 1 commit intotigera:release-v1.40from
tianfeng92:fix-kibana-discard-unknown-objects-v1.40
Apr 23, 2026
Merged

[release-v1.40] fix(kibana): discard unknown saved objects on upgrade from 7.x#4744
marvin-tigera merged 1 commit intotigera:release-v1.40from
tianfeng92:fix-kibana-discard-unknown-objects-v1.40

Conversation

@tianfeng92
Copy link
Copy Markdown
Contributor

Summary

Cherry-pick of #4741 onto release-v1.40 for CE 3.22.

Release Note

Fix Kibana crashloop when upgrading from Calico Enterprise 3.20 or earlier to 3.22. The orphan `ingest_manager_settings` saved object left by Fleet 7.17 is now discarded during Kibana 8.x saved-object migration.

Note on CE 3.22.2

CE 3.22.2 ships a tigera/kibana:v3.22.2 image containing an 8.19.10 Kibana binary, while operator release-v1.40 has ComponentEckKibana.Version = "8.19.12" (anticipating the 3.22.3 image rebuild). Until 3.22.3 ships, customers running 3.22.2 will see Kibana ignore the discard setting with The flag migrations.discardUnknownObjects is defined but does not match the current kibana version. Those customers should use the manual workaround with "8.19.10" documented on the parent ticket. This fix takes effect automatically from 3.22.3 onward (image + operator aligned).

🤖 Generated with Claude Code

Set migrations.discardUnknownObjects to the running Kibana version so
CE 3.20 -> 3.21+ upgrades don't crashloop on the orphan
ingest_manager_settings document left behind by Fleet 7.17 after v1.38
disabled the Fleet plugin.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@rene-dekker
Copy link
Copy Markdown
Member

/merge-when-ready

@marvin-tigera
Copy link
Copy Markdown
Contributor

OK, I will merge the pull request when it's ready, leave the commits as is when I merge it, and leave the branch after I've merged it.

@marvin-tigera
Copy link
Copy Markdown
Contributor

I'm sorry but I failed to merge the pull request even though it's ready to merge.

2 similar comments
@marvin-tigera
Copy link
Copy Markdown
Contributor

I'm sorry but I failed to merge the pull request even though it's ready to merge.

@marvin-tigera
Copy link
Copy Markdown
Contributor

I'm sorry but I failed to merge the pull request even though it's ready to merge.

@tianfeng92 tianfeng92 marked this pull request as ready for review April 23, 2026 20:05
@tianfeng92 tianfeng92 requested a review from a team as a code owner April 23, 2026 20:05
@marvin-tigera marvin-tigera merged commit dab32ff into tigera:release-v1.40 Apr 23, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants