As far as I understand, ECK will generate a password and place it in a secrets file. This doesn't suit our workflow, we want to provide known values for all things upfront, including the elastic user password. Is there a way to provide it instead of having it auto-generated? As far as I can see, the documentation at least doesn't mention it.
For what its worth, I used this approach and it works fine. It does require creating the secret in advance... How to give built password in ECK CR
Thanks! I noticed that workaround after I posted. We'll do the same.