Trying to update or rather install the latest version of the chart, but hitting an issue with the advanced visibility setup.

[smolinari]

Hi,

I'm almost there. However, I set up an index in ES now with username and password, and I'm getting this during the setup job.

Any tips of what might be wrong would be greatly appreciated. It might be a permissions issue. I'm not an ES expert (more like a total noob), so I'll go play with the settings. But, if anyone has any direct idea, I'm all ears.

Also, if someone could, explain this warning to me please. It isn't making complete sense to me:

Warning: Starting from temporal >= 1.21 standard visibility becomes advanced visibility. Advanced visibility configuration is now moved to standard visibility. Please only use visibility datastore configuration. Advanced visibility store usage will be forbidden by the operator for clusters >= 1.23.

Scott

[smolinari]

Ok. It's not permissions. I opened them to "all" for the user's role and still the same "Empty reply from server". I'm creating a new cluster too btw.

Scott

[smolinari]

Ok. Got a step closer. The connection URL was missing the "s" in "https". Since I turned on the security in ES, the connection requires SSL.

But now I'm getting this in the job:

At least I know where to head with this error. 😁

Scott

Scott

[alexandrevilain]

Hi @smolinari !

It looks like it's a bug on the operator side. The generated value is wrong.

It will take a look as soon as possible!

[smolinari]

That would be so awesome!!! Thanks! 🙏

Scott

[smolinari]

Also I need some clarification. I was looking at what I believe is the code for setting up the name to the file ref and noticed the logic is about volumes.

Does that mean I have to also do an override to get a secret set up as a volume in the container?

Scott

[alexandrevilain]

Hi @smolinari !

This will be fixed in #732

[smolinari]

@alexandrevilain - Appreciate it. Can you let me know if my concern above is also warranted? I'm not certain about how I should be pulling in the database credentials as secrets.

Scott