Skip to content

[Fleet] Update fleet mappings version #119087

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Dec 19, 2024

Conversation

nchaulet
Copy link
Member

Description

Resolve elastic/kibana#204834

Update mappings version for .fleet systems indices, we made a few change to .fleet indices without updating the mappings version. The consequence of this is the mappings are not updated on stack upgrade.

That PR fix that by increasing the mapping version for those indices.

How to tests?

I tested the upgrade from an 8.12 Elasticsearch to 8.18 than to that version with

yarn es  source -E xpack.security.authc.api_key.enabled=true -E xpack.security.authc.token.enabled=true  --source-path=/Users/nchaulet/Workspace/elasticsearch  -E path.data=/tmp/es-data

And I was able to verify the .fleet indices have updated mappings, especially the namespaces: keyword that is required for Fleet space awareness

@nchaulet nchaulet added auto-backport Automatically create backport pull requests when merged Team:Fleet v8.18.0 labels Dec 19, 2024
@nchaulet nchaulet self-assigned this Dec 19, 2024
@nchaulet nchaulet requested a review from a team as a code owner December 19, 2024 14:15
@elasticsearchmachine
Copy link
Collaborator

@nchaulet please enable the option "Allow edits and access to secrets by maintainers" on your PR. For more information, see the documentation.

@elasticsearchmachine elasticsearchmachine added v9.0.0 external-contributor Pull request authored by a developer outside the Elasticsearch team labels Dec 19, 2024
@nchaulet nchaulet added :Core/Infra/Core Core issues without another label Team:Core/Infra Meta label for core/infra team labels Dec 19, 2024
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra (Team:Core/Infra)

@nchaulet nchaulet merged commit 2c5bcdd into main Dec 19, 2024
17 checks passed
@nchaulet nchaulet deleted the feature-update-fleet-mappings-version branch December 19, 2024 19:21
@elasticsearchmachine
Copy link
Collaborator

💚 Backport successful

Status Branch Result
8.x

@elasticsearchmachine
Copy link
Collaborator

💔 Backport failed

The backport operation could not be completed due to the following error:

There are no branches to backport to. Aborting.

You can use sqren/backport to manually backport by running backport --upstream elastic/elasticsearch --pr 119087

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-backport Automatically create backport pull requests when merged backport pending :Core/Infra/Core Core issues without another label external-contributor Pull request authored by a developer outside the Elasticsearch team >non-issue Team:Core/Infra Meta label for core/infra team Team:Fleet v8.18.0 v9.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Fleet] .fleet-* system indices mappings are not updated on stack upgrade
3 participants