Incompatibility with ECK (official elastic operator for Kubernetes deployment)

Was this something that was able to be resolved?
I am trying the same thing and an unable to even disable security with 7.8.

This is next in line in our current sprint for @clutroth

Do you have an ETA for when it will be deployed and usable in this state? And will it secure both elastic and kibana still?

we will provide more info on this on Monday.

we have just released ROR 1.50.0 with ECK support.

You have to enable xpack security (xpack.security.enabled: true ) and patch Elasticsearch after installing ROR. Moreover, you have to use xpack security SSL for HTTP and transport.

The documentation is not updated yet.

I would also welcome an update to the documentation. Releasing functionality without documentation is half-baked
Thanks
Rudolf

Hi @rjan, you are so right about this.

We were in a hurry to merge ECK support because that branch was rapidly diverging from the main one.
Our pilot customer was already sufficiently happy with ROR+ECK, so we decided to merge it and continue working on the main branch.

As a result, the code is out, but the truth is that the tooling and documentation still does not make the feature usable.

We can do two things:

  • prioritize further ECK examples simplification & documentation
  • Follow up with you @rjan on ECK guidance as a support request