-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Align the version of Elasticsearch/Logstash/Kibana (7.16) across all integration tests and documentation #25663
Align the version of Elasticsearch/Logstash/Kibana (7.16) across all integration tests and documentation #25663
Conversation
e4da5a3
to
c77f8a7
Compare
This comment has been minimized.
This comment has been minimized.
…n of logging-gelf Because older versions don't support Elasticsearch 7.10. See https://archivedocs.graylog.org/en/latest/pages/configuration/elasticsearch.html See https://docs.graylog.org/docs/installing#system-requirements
…tion tests and documentation
c77f8a7
to
79a45eb
Compare
This comment has been minimized.
This comment has been minimized.
…ration tests docker.elastic.co has been down a few times in the past, dockerhub is more reliable. They both serve the exact same images (same tags, same hashes), so the change should be mostly transparent.
1. Because we don't use it (we always connect unauthenticated) 2. Because we'll need to disable it in Elasticsearch 8+ anyway, otherwise Elasticsearch uses a self-signed certificate (which we have to allow in the client JVM) and mandates HTTP authentication.
79a45eb
to
4076577
Compare
Failing Jobs - Building 4076577
Full information is available in the Build summary check run. Failures⚙️ Devtools Tests - JDK 11 #- Failing: integration-tests/devtools
📦 integration-tests/devtools✖
⚙️ Devtools Tests - JDK 17 #- Failing: integration-tests/devtools
📦 integration-tests/devtools✖
⚙️ Native Tests - HTTP #- Failing: integration-tests/resteasy-reactive-kotlin/standard
📦 integration-tests/resteasy-reactive-kotlin/standard✖
|
@quarkusio/devtools the |
@gastaldi AFAICS from the bot's report, it's this thing throwing the exception: |
@@ -103,11 +102,12 @@ version: '3.2' | |||
|
|||
services: | |||
elasticsearch: | |||
image: docker.elastic.co/elasticsearch/elasticsearch-oss:{es-version} | |||
image: {elasticsearch-image} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to include this attribute here:
https://github.com/quarkusio/quarkusio.github.io/blob/develop/_guides/attributes.adoc
Let's do it now so that we don't forget about it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here you go: quarkusio/quarkusio.github.io#1438
I don't really know what I'm doing though; I would have expected this file to be generated. Should I remember to keep it in sync every time we upgrade to a new version of Elasticsearch?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah unfortunately it's not generated. It wasn't when I took over the role and I never took the time to think about how to do this properly.
As requested by @gsmet [here](quarkusio/quarkus#25663 (review)). See https://github.com/quarkusio/quarkus/pull/25663/files#diff-749f6f9897e14f3c05890960c13ad402b7541d714116175a61cada4e64f085a1R2827-R2829 See https://github.com/quarkusio/quarkus/pull/25663/files#diff-150bdf617c2dc80dc5a9d5f1313f44a73950a96ca7b166b79a35b15f4c84f193R79-R82
As requested by @gsmet [here](quarkusio/quarkus#25663 (review)). See https://github.com/quarkusio/quarkus/pull/25663/files#diff-749f6f9897e14f3c05890960c13ad402b7541d714116175a61cada4e64f085a1R2827-R2829 See https://github.com/quarkusio/quarkus/pull/25663/files#diff-150bdf617c2dc80dc5a9d5f1313f44a73950a96ca7b166b79a35b15f4c84f193R79-R82
Context: #25648 (comment)
In short, we need at least Elasticsearch 7.11 to run on Apple M1, and the heterogeneous configuration made upgrading the Elasticsearch version difficult.
This makes the Elasticsearch container configuration consistent across all integration tests and bumps the Elasticsearch server version used for tests to 7.16 (also Logstash and Kibana, so technically we're upgrading the whole ELK stack).
I didn't change the version of the client, in particular the High Level REST client, which cannot be upgraded beyond 7.10 because 7.11+ is no longer open-source. However, that's no big deal as the High Level REST client is forward-compatible with Elasticsearch (server) 7.16. We will have a problem when we want to upgrade to Elasticsearch 8.x, but that's a problem for another day.