lowess / helm-charts

Open source repository for Kubernetes Helm Charts

Helm-Charts

The release process of this repository is managed by chart-releaser and a Drone CI/CD pipeline

Getting Started

helm repo add lowess-helm-charts https://lowess.github.io/helm-charts/

helm-charts's Issues

Helm repo giving 404 error

https://lowess.github.io/helm-charts/ does not work

Add zoonavigator helm chart

Add helm chart for https://github.com/elkozmon/zoonavigator

TLS configuration issue

I am using below config in values.yaml and running into an issue.
Would someone be able to tell if there is any issue in the config?

Maps to [client-profile] section in burrow.toml

clientProfile:
  ## clientProfile configures a Kafka profile to use by Burrow consumer.
  main:
    kafkaVersion: "2.2.1"
    clientId: "burrow-test"
    tls: "msk-mTLS"

tls: {}
  msk-mTLS:
    certFile: "/tmp/client_cert.pem"
    keyFile: "/tmp/private_key.pem"
    caFile: "/tmp/truststore.pem"

Error:
Error: render error in "burrow/templates/burrow-deployment.yaml": template: burrow/templates/burrow-deployment.yaml:16:28: executing "burrow/templates/burrow-deployment.yaml" at <include (print $.Template.BasePath "/burrow-configmap.yaml") .>: error calling include: template: burrow/templates/burrow-configmap.yaml:30:18: executing "burrow/templates/burrow-configmap.yaml" at <.Values.burrow.config.tls>: nil pointer evaluating interface {}.burrow

HTTP notifier headers

Hi! Thank you for putting together these charts.

I'm interested in the Burrow one, but I need an addition—that I'm willing to contribute. In order to create alerts using Opsgenie's API, I need to set the Authorization header in notifier requests. This is possible by setting notifier.<my-notifier>.headers. In order to keep my API key secure, I'd use an env var loaded from a secret. Do you think this is a good approach?

Just to be sure, there's no way to set the headers option with the chart as it currently stands, or is there?

Also, you don't have a LICENSE file so could you please comment on whether I'm free to use this (and change it)?

Missing IngressClassName field in ingress templates in zoonavigator (and possibly others)

Hi.

In the ingress template, you are defining it's class via annotation which is depreciated method.
https://kubernetes.io/docs/concepts/services-networking/ingress/#deprecated-annotation

On newer k8s installations, there is no way of definig ingress class (annotation is ignored).

Add possibility to specify custom pod annotations for Burrow

Hi there.

We would like to have a possibility to specify custom pod annotation.

Usecase: to sync pods to consul services with katalog-sync custom annotations should be specified.

We can come with PR if this speeds up the process of getting this small feature available.

Add possibility to specify 'client-profile' for clusters

According to Burrow configuration documentation, it's possible to specify client-profile for cluster.

But that's not possible with the current chart (it's possible to specify client-profile for consumer though).

Please add support of this configuration option.

We are glad to contribute and prepare PR.

Support Kubernetes 1.22

Trying the helm chart for Zoonavigator. To support k8s 1.22, it means using networking.k8s.io/v1 for Ingress. I'm getting

unable to recognize "": no matches for kind "Ingress" in version "networking.k8s.io/v1beta1"

Downgrading my k8s cluster to 1.21 for now... My client's clusters have upgraded to 1.22 so need to fix this.

Make TLS options available

Hi,
Thank you for creating these charts!

I'd like to use this to monitor AWS MSK clusters w/ TLS option enabled.
According to this documentation I need some additional config options to connect to my brokers through port 9094.

E.g.:

[client-profile.msk1-client]
client-id="burrow-test"
tls="msk-mTLS"
kafka-version="2.0.0"

and

[tls.msk-mTLS]
certfile="/tmp/client_cert.pem"
keyfile="/tmp/private_key.pem"
cafile="/tmp/truststore.pem"
noverify=false

It would be great if these would be available in this helm chart.

Add support for providing configuration over Secrets

This feature would be helpful for deployments where, for example, Zookeer hosts are stored in k8s secret or in external secret (https://github.com/godaddy/kubernetes-external-secrets). And with the help of Reloader (https://github.com/stakater/Reloader), it's possible that changing of secrets makes re-deployment of Burrow pod.

In our workflow, we are using Amazon MSK and after scaling of the cluster, we automatically update SSM Parameter with a new list of Zookeeper hosts and that change triggers re-deploy of Burrow with a new configuration provided by External Secret. In that way, we do not have to make any manual changes to have the whole Kafka cluster monitored after scaling.

I think these changes could be valuable for others because they are providing additional flexibility to the chart configuration.

Bump Karrot to use Burrow latest