Upgrade Elastic Stack 8 to 8.19.21 - #2563
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
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
1 participant
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.
Summary
mapper-size), all-in-one app base, AppHost defaults, Docker Compose/samples, Helm values, and production/dev/monitoring Elasticsearch, Kibana, APM, and Agent version pins.main, independent of the ES9 base PR Upgrade Elasticsearch to 9.5.3 #2416 and experiment Experiment with ES|QL lookup joins for event and stack queries #2511. No JOIN queries, application schema changes, or index-format reindexing are included.Compatibility, security, and rollout
This is an 8.19 patch upgrade; application APIs, queries, index schemas, and the existing Elasticsearch .NET client 8.19.23 are unchanged. No bulk reindex is required by this PR. It is the rollout step before considering Elasticsearch 9, not an authorization to apply production manifests.
The patch includes fixes for Elasticsearch request smuggling, CVE-2026-78605, inference authorization, CVE-2026-78607, and Kibana Fleet authorization, CVE-2026-82302. This is not an exhaustive image vulnerability scan.
Reviewed the intervening 8.19.16–21 release notes. Upstream behavior changes to check for custom deployments: ILM allocation now clears auto-expanded replicas when an explicit replica count is supplied; inference secrets cannot be overridden; Kibana email connectors validate HTTPS-proxy certificates by default. No affected configuration was found in the checked-in application/deployment settings. Preserve TLS verification and supply a trusted proxy certificate where needed.
8.19.21 was released September 2 and is less than two weeks old: use a staging soak, a current restore-tested snapshot, and a controlled ECK rolling upgrade with shard recovery/health checks. Publish/verify the custom 8.19.21 image before applying its deployment pins. Do not downgrade an upgraded data directory or delete volumes; keep the approved snapshot/recovery procedure available. ECK itself is unchanged by this PR.
Verification
elasticsearchdependency; its unrelated fix was removed as requested. The other four Compose configurations validate.Sources: 8.19.21 release announcement, Elasticsearch 8.19 release notes, Kibana 8.19.21 notes.