* Add '"' to ensure match only on expected password placeholder
Signed-off-by: Niels F. S. Vistisen <nfsv@trifork.com>
* Bump chart version
Signed-off-by: Niels F. S. Vistisen <nfsv@trifork.com>
* Correct property being bumped
Signed-off-by: Niels F. S. Vistisen <nfsv@trifork.com>
---------
Signed-off-by: Niels F. S. Vistisen <nfsv@trifork.com>
* Added the possibility to add additional Kafka configuration via a
secret. Either via providing name of existing secret, or providing the
value for a secret the chart then creates.
Signed-off-by: Lucas Petersen <lux_-4@hotmail.com>
* Bumping Chart.yaml
Signed-off-by: Lucas Petersen <lux_-4@hotmail.com>
* readme-generator
Signed-off-by: Lucas Petersen <lux_-4@hotmail.com>
* Added support for oauthbearer sasl mechanism
Signed-off-by: Lucas Petersen <lux_-4@hotmail.com>
* minor version bump
Signed-off-by: Lucas Petersen <lux_-4@hotmail.com>
* Fixed small oversight where controller specific sasl credentials wasn't dependent on mechanism
Signed-off-by: Lucas Petersen <lux_-4@hotmail.com>
---------
Signed-off-by: Lucas Petersen <lux_-4@hotmail.com>
Signed-off-by: LuxTheDude <lux_-4@hotmail.com>
Signed-off-by: Jose Antonio Carmona <jcarmona@vmware.com>
Co-authored-by: Jose Antonio Carmona <jcarmona@vmware.com>
* Added the possibility to add additional Kafka configuration via a
secret. Either via providing name of existing secret, or providing the
value for a secret the chart then creates.
Signed-off-by: Lucas Petersen <lux_-4@hotmail.com>
* Bumping Chart.yaml
Signed-off-by: Lucas Petersen <lux_-4@hotmail.com>
* readme-generator
Signed-off-by: Lucas Petersen <lux_-4@hotmail.com>
---------
Signed-off-by: Lucas Petersen <lux_-4@hotmail.com>
Since version 24 the chart no longer supports reading PEM files
containing key material from an existing secret provided by
cert-manager. Instead, the init container now expects to find a
certificate file "kafka.crt" and a private key file "kafka.key" and a CA
file "kafka.ca.crt".
The shell script used by the init container to create the JKS keystore
for the Kafka broker process has been adapted to also accept the
standard file names used by cert-manager again.
Signed-off-by: Kai Hudalla <sophokles.kh@gmail.com>
Signed-off-by: Miguel Ruiz <miruiz@vmware.com>
Co-authored-by: Miguel Ruiz <miruiz@vmware.com>
* fix: set domain is ineffective when autoDiscovery
--set externalAccess.service.domain is ineffective when --set externalAccess.autoDiscovery.enabled=true
Signed-off-by: lkad <eloony@163.com>
* kafka change version
Signed-off-by: lkad <eloony@163.com>
* Update scripts-configmap.yaml
Signed-off-by: lkad <eloony@163.com>
* Increase the priority of domain configuration to the highest
Increase the priority of domain configuration to the highest when externalAccess.service.type is "NodePort"
Signed-off-by: lkad <eloony@163.com>
* Update scripts-configmap.yaml
Signed-off-by: lkad <eloony@163.com>
---------
Signed-off-by: lkad <eloony@163.com>
* [bitnami/kafka] Fix issue with Kafka where Zookeeper mode could not be used + minor fixes
Signed-off-by: Miguel Ruiz <miruiz@vmware.com>
* Revert values.yaml changes
Signed-off-by: Miguel Ruiz <miruiz@vmware.com>
---------
Signed-off-by: Miguel Ruiz <miruiz@vmware.com>
- Introduce settings value externalAccess.service.externalIPs - see issue #14222.
- Add default and documentation in default values.
- Add validator for new faeture and modify logic of nodePorts accordingly.
- Make slicing of NodePorts output more robust if length is by mistake lower current index.
Signed-off-by: Jens W. Klein <jk@kleinundpartner.at>
* Add support set config broker.rack with AWS availability zone info
Signed-off-by: DingGGu <ggu@dunamu.com>
* Remove default brokerRackAssignment value
Signed-off-by: DingGGu <ggu@dunamu.com>
* Update README.md with readme-generator-for-helm
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
* doc: Add missing padding in README.md
Signed-off-by: DingGGu <ggu@dunamu.com>
* Provide broker rack information to same way with MSK
Signed-off-by: DingGGu <ggu@dunamu.com>
Signed-off-by: DingGGu <ggu@dunamu.com>
Signed-off-by: Bitnami Containers <bitnami-bot@vmware.com>
Signed-off-by: Carlos Rodríguez Hernández <carlosrh@vmware.com>
Co-authored-by: Bitnami Containers <bitnami-bot@vmware.com>
Co-authored-by: Carlos Rodríguez Hernández <carlosrh@vmware.com>
logsDir is for kafka's log segment, not kafka logs from log4j
Signed-off-by: Cyril Jouve <jv.cyril@gmail.com>
Signed-off-by: Cyril Jouve <jv.cyril@gmail.com>
Co-authored-by: Francisco de Paz Galán <fdepaz@vmware.com>
Changes about PR bitnami/charts#8983
* Include new variable to allow set external names for external listeners. This fixbitnami/charts#8875
* Remove loadbalancersIPs validations from NOTES.txt and include loadBalancerAnnotations parameter to allow users set different annotations for each external load balancer
Co-authored-by: Juan Ariza Toledano <juanariza@vmware.com>
Signed-off-by: Fran Mulero <fmulero@vmware.com>
* Ignore the build folder
* Update the Makefile
* Support using MY_POD_IP env variable for external access
* Update comment for configuration value
* Support usePodIPs
* Remove unused file
* Update scripts-configmap.yaml
Correct the syntax
* Increase the patch version for the change
* Update the README.md for new configuration value usePodIPs
* Update scripts-configmap.yaml
Update the if else logic
Previous Updated:
```
{{- if or .Values.externalAccess.service.useHostIPs .Values.externalAccess.autoDiscovery.enabled }}
export EXTERNAL_ACCESS_IP="${HOST_IP}"
{{- else if or .Values.externalAccess.service.usePodIPs .Values.externalAccess.autoDiscovery.enabled }}
export EXTERNAL_ACCESS_IP="${MY_POD_IP}"
```
To new
```
{{- if and .Values.externalAccess.service.usePodIPs .Values.externalAccess.autoDiscovery.enabled }}
export EXTERNAL_ACCESS_IP="${MY_POD_IP}"
{{- else if or .Values.externalAccess.service.useHostIPs .Values.externalAccess.autoDiscovery.enabled }}
export EXTERNAL_ACCESS_IP="${HOST_IP}"
```
The previous logic will ignore the `usePodIPs` flag when `.Values.externalAccess.autoDiscovery.enabled` is true and system will use HOST_ID instead of usePodIPs = true.
By combine the `Values.externalAccess.service.useHostIPs` & `.Values.externalAccess.autoDiscovery.enabled` it will make sure we will use MY_POD_IP. For other cases it will use HOST_IP
Co-authored-by: Ryan Nguyen <ryan.nguyen@shopback.com>
* [bitnami/kafka] Use autoDiscovery values for NodePort external access
If externalAccess is enabled and the service is NodePort the `EXTERNAL_ACCESS_IP` value is not used when writing the `setup.sh` script.
* Bump Chart version
* Update bitnami/kafka/Chart.yaml
Co-authored-by: Andrés Bono <andresbonojimenez@gmail.com>
Co-authored-by: Kerins, Marc <Marc.Kerins@bluvector.io>
Co-authored-by: Andrés Bono <andresbonojimenez@gmail.com>
