Peter Brachwitz
Peter Brachwitz
I am trying to understand what the use case for this would be. You can create a single node cluster without setting the `discovery.type` to `single-node`. Can you exlain?
buildkite test this -f s=8.16.0-SNAPSHOT,E2E_TAGS=kb -m p=ocp
I think you need to version gate this to 7.x or greater. We still need to support 6.x and Kibana does not work with the restricitive security context in 6.x...
Also in more recent versions. I am testing 7.13 here it seems while Kibana comes up with the security context. The reporting feature will be broken: ``` Error: EROFS: read-only...
> I think you need to version gate this to 7.x or greater. We still need to support 6.x and Kibana does not work with the restricitive security context in...
What you are trying to do is currently not supported. The operator, as you have found out is not aware of the `server.basePath` setting. The only work around I can...
I am on the fence whether this should be triaged as bug or enhancement. I'm tending towards enhancement because the `health` indicator on the custom resources as has traditionally in...
I think we could simply relax the validation. This case was not considered when this code was written.
I intially thought this was a bug but the problem stems from the fact that you are configuring the same TLS secret you use for the HTTP layer of Elasticsearch...
> > We currently do not support chains in the custom CAs that you can configure there > > Why does TransportTLSOptions not support chains? Is there a specific reason?...