* Use template for log4j configuration
This will allow you to use variables in the log4j configuration
log4j: |-
log4j.rootLogger={{ default "INFO" .Values.logLevel }}, stdout, kafkaAppender
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=[%d] %p %m (%c)%n
* Version bumped
* Update bitnami/kafka/templates/log4j-configmap.yaml
Co-authored-by: Marcos Bjoerkelund <marcosbc@users.noreply.github.com>
* Switch to the bitnami's standard for tpl values
Co-authored-by: Marcos Bjoerkelund <marcosbc@users.noreply.github.com>
* [bitnami/thanos] allow overriding service selectors
Allow overriding of selectors for all thanos components services. If the value labelSelectorsOverride stays empty, current behavior with default labels is used.
* fix: resolve PR comments
* Remove component label when using labelSelectorsOverride
Co-authored-by: Andrés Bono <andresbono@vmware.com>
* [bitnami/external-dns] add support for aws-api-retries arg
* Bump chart version
* Document variable in README
* Apply suggestions from code review
Co-authored-by: Francisco de Paz Galán <fdepaz@vmware.com>
* Use default value
Co-authored-by: Francisco de Paz Galán <fdepaz@vmware.com>
* Force redis-exporter to use TLS
* Version update
Co-authored-by: Jaak Pruulmann-Vengerfeldt <jjpp@cyber.ee>
Co-authored-by: Miguel Ángel Cabrera Miñagorri <macabrera@bitnami.com>
* Only render yaml keys that are lists when there are actual values for them
* Bump chart version
* Fix condition on volumeMounts for init cluster job
* Remove extra newline
* Fix volumeclaim selector
* Make linter happy
Co-authored-by: Andrés Bono <andresbono@vmware.com>
Add the /bin/sh -cx command in front of the "chown" stuff to avoid "file
not found" and similar errors. Similar to how it's done in the Postgres
chart.
Signed-off-by: Thorsten Klein <iwilltry42@gmail.com>
* Set metrics exporter CA certificate env variable
Add the REDIS_EXPORTER_TLS_CA_CERT_FILE environment variable to the prometheus exporter
https://github.com/oliver006/redis_exporter/issues/387 has been resolved
* Bump redis chart version to 11.3.0
* Set metrics exporter CA certificate env variable
Add the REDIS_EXPORTER_TLS_CA_CERT_FILE environment variable to the prometheus exporter
https://github.com/oliver006/redis_exporter/issues/387 has been resolved
* Bump redis-cluster chart version to 3.3.0
* allow custom values for liveness and readiness probe
* end file in newline
* remove trailing spaces
* add enabled flag to livenessProbe and readinessProbe
Co-authored-by: Bonadio, Michael <bonadm1@nationwide.com>
extra manifests declared with the `extraDeploy` value used to be defined in a single List manifest.
the issue with this setup, is that if you want to define a Job to be used as a Helm hook, it won't work - because Helm only look at top-level manifests to find the hook annotations.
this PR changes the implementation of extra manifests, by rendering top-level manifests instead of wrapping them inside a List.
charts users don't need to change anything in their values.yaml