Conversation
…onfig.replaceConfigMap couldn't be set
juldrixx
left a comment
There was a problem hiding this comment.
The two replaces (configmap vs. secret) are complementary, not exclusive. You can define the 2 and the result is a fusion of the 2.
https://github.com/konpyutaika/nifikop/blob/master/pkg/resources/nifi/secretconfig.go#L341-L361
The Helm should therefore make it possible to specialise in both independently. And in your change, it's either one or the other.
|
Thanks for the info, I didn't realise you could set both! I think the helm-chart is still incorrectly applying a default logback in it's current configuration though. If I use the following helm values: because |
There is no "default" logback configuration. If you don't set |
The nifi-cluster helm chart will use this configuration if there's not one provided as an override: https://github.com/konpyutaika/nifikop/blob/master/helm/nifi-cluster/config/logback.xml But there's actually a bug here where it's not possible to override the So that logic needs updating and perhaps the helm chart should not even provide a default and let the operator generate it from the template you've linked. But because there's a default in the helm chart, the operator's template won't be used as currently written. |
What's in this PR?
The current
cluster.logbackConfiglogic in the nifi-cluster helm chart doesn't allow a user to override the logback.xml with a configMap.Additional context
Currently if you set
cluster.logbackConfig.replaceConfigMapand omitcluster.logbackConfig.replaceSecretConfig, the default secret value is added to the NiFiCluster, as well as the configmap value - setting both.This change allows a user to set either replaceSecretConfig or replaceConfigMap and if unset, falls back to the default.
Checklist