Chart advice about charts

[drpebcak]

It is possible to put Postgres and Elasticsearch back in the chart and use a bool for enable: etc to pull in as needed. This creates a chart that can be spun up fully without external dependencies or allow external instances. Just an opinion.

I would rather not, because managing those dependencies makes this chart a lot heavier. Having to keep those up to date and then worry about breaking changes inside those downstream charts is more work than it is worth. I personally also don't like tying state into a chart for a stateless service.

Also what is the desired result for these sections. They do not work as one expects

To use an existing secret, set existingSecret to the name of the secret. We expect two keys: password and rootpassword
existingSecret: "" <----- If this is filled in then the next fields should be ignored, not required
user: ""
password: ""

These credentials are used for bootstrapping the database
root:
user: "" <----- if the secret is filled in then this should be ignored (?)
password: ""

Not sure what you are getting at here. The user is still required - only the passwords are coming from the secret. The comment says: We expect two keys: password and rootpassword. I've seen secrets done both ways - with the username as part of the secret and not. Is the comment not clear that we are only filling in password and rootpassword?

search:
Valid values for engine are 'elasticsearch' or (if you are using fusionauth >= 1.16.0-rc.1) 'database'.
engine: elasticsearch <----- If you place database here should this not cause the host field to be ignored?
protocol: http
host: ""

This is how it works, isn't it? If you set search.engine=database, nothing that uses search.host is used.

[DarkBlaez]

Actually the chart is not working correctly. Deploy with "database" over "Elasticsearch" and check the logs, there are exceptions thrown. Also, the reasoning behind the chart inclusion actually does not hold merit. Being able to include as needed has never been much of an issue for other maintainers or projects, to include competitors. It's a very simple task if helm is well understood. However, what I will do is reformulate the charts and publish an alternative set which mirror what others are doing. Thanks for the clarification

DB

[drpebcak]

The issue you are referring to doesn't have anything to do with the chart, it was an issue in the default version of the application. You can see it being discussed here: FusionAuth/fusionauth-issues#851

We can of course bump up the version of fusionauth we are installing.

[DarkBlaez]

If that is the issue then we should bump the version being pulled

Thanks
DB

[drpebcak]

Just did it.