Unable to connect to Elastic with specified elastic user

[skirven4]

Elastic Support Case: 01644420

Issue: I created a static secret for the elastic user per the documentation: https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-users-and-roles.html. The user works as expected in Elastic and Kibana.

The issue is that because of the secret not being created, the Diagnostic script cannot login:
"If you specify the password for the elastic user through such a basic authentication secret then the secret holding the password described in Default elastic user<https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-users-and-roles.html#k8s-default-elastic-user> will not be created by the operator."

Shouldn't the Diagnostic app try to use the secret user if it's available from the deployment? Or maybe ECK should create the secret if it's not present for this reason?

[thbkrkr]

Shouldn't the Diagnostic app try to use the secret user if it's available from the deployment?

To be able to do that, we would need to put more knowledge about the ECK operator into the eck-diagnostics code and that is not something we want to do.

Or maybe ECK should create the secret if it's not present for this reason?

That will not work when users want no default elastic user, see:

• Potentially allow disabling the creation of the elastic user. cloud-on-k8s#7719

Since ECK 2.13.0, the operator creates a dedicated user for the eck-diagnostics, independent of the elastic user. This should cover your case?

• Allow disabling of elastic user. cloud-on-k8s#7723

[skirven4]

Aha! That makes total sense. I did search some through the code but was not sure what I was looking for. I need to upgrade the operator very soon.
Thank you!!

Edit: I did see the notes about the disabling of the elastic user in 2.13.0, but wasn't sure if thr connection to the Diagnostic had been corrected.