feat(elasticsearch): reenable - #304
Merged
Merged
Conversation
maevsi-bot
pushed a commit
that referenced
this pull request
Sep 7, 2026
## [21.2.0](21.1.0...21.2.0) (2026-09-07) ### Features * **elasticsearch:** reenable ([#304](#304)) ([3894748](3894748))
|
🎉 This PR is included in version 21.2.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
Elasticsearch has been scaled to zero since April 2026 and Zammad's integration with it was switched off a month later, so the helpdesk has been running without a search index ever since.
This reenables both.
The connection stays on HTTPS.
The certificate Elasticsearch generated for itself on first start is already imported into Zammad, and
network.publish_hostputselasticsearchinto that certificate's subject alternative names, so verification succeeds against the hostname Zammad connects to.http.max_content_lengthis raised to 400mb because Zammad'ses_total_max_size_in_mbdefaults to 300, above Elasticsearch's 100mb limit, which would otherwise fail the index rebuild.The healthcheck that was commented out is enabled unchanged, since it works as written.
docs/elasticsearch.mdis new.It records where the certificate comes from, how it gets into Zammad, and that neither the authority nor the server certificate is ever renewed automatically.
The server certificate expires around February 2028, after which search stops working until it is reissued by hand.
Zammad 7.1 supports Elasticsearch 9.x, and
ingest-attachmentships as a bundled module there rather than a plugin, so nothing extra is needed for attachment indexing.The Elasticsearch side is verified against a real 9.5.3 node;
zammad-initactually building the index has not been exercised end to end.