Chance Zibolski

@alex-zaitsev sure, that seems reasonable. So next to the `secret` field I added then?

If we move it from the host configuration, how is this supposed to be configured for the auto-generated clusters? https://github.com/Altinity/clickhouse-operator/blob/master/pkg/model/ch_config_generator.go#L336-L398

@alex-zaitsev Thoughts on how to deal with configuring auto generated clusters when internode authentication is configured?

@alex-zaitsev Sounds good. I can rebase and I think this PR is pretty close to the configuration you've suggested, so hopefully this can be merged soon then.

@alex-zaitsev I'm looking back into this but my question from earlier is still unanswered: > Thoughts on how to deal with configuring auto generated clusters when internode authentication is configured?...

I also hit this. Needs to be possible to set this to secure in the hostTemplates, or somewhere similar.

The config files have to live at `$HIVE_HOME/conf` (currently `/opt/hive-2.3.3`), and `$HIVE_HOME` has to be in the rootfs, not tmpfs as it's got the entire hive installation. The config files...

I started this in #666.

Can you try an install with your PSP and set both `spec.presto.hive.server.image.tag` and `spec.presto.hive.metastore.image.tag` to `pr-666` in your Metering CR?

I'll also give it a try and see if we can just default to `readOnlyRootFilesystem` in our pods securityContexts.