-
Notifications
You must be signed in to change notification settings - Fork 229
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
[DO_NOT_MERGE] Logging upgrade #208
Conversation
90af3c9
to
7d417c3
Compare
There seems to be some strangeness with SG initializing itself when there are multiple nodes in the cluster. I'm going to investigate seeding SG sooner in the openshift-elasticsearch-plugin... |
dd5e6b7
to
8d89b37
Compare
find the troublesome record:
|
fd49e77
to
558673a
Compare
558673a
to
161926c
Compare
99429e1
to
e110284
Compare
Evaluated for aggregated logging test up to e110284 |
Aggregated Logging Test Results: FAILURE (https://ci.openshift.redhat.com/jenkins/job/test-origin-aggregated-logging/758/) |
closing in favor of #219 |
@sosiouxme @jcantrill @richm PTAL - this isn't to be merged in, but will be used for QE to test from.
I plan to update the Readme as well to cover topics such as de-dotting and to update the health-check information. Also it having a PR will allow it to go through the CI testing process.
Other things to note:
SG currently doesn't let us configure its index. [1]
And if I remember correctly we are impacted by this when trying to connect to another ES node for clustering (will retest) [2]
[1] https://github.com/floragunncom/search-guard/issues/176
[2] https://github.com/floragunncom/search-guard/issues/153