utkuozdemir / helm-charts

Helm Chart Repository

Hi there, I'm Utku Ozdemir 👋

helm-charts's Issues

Add possibility to mount hostpath to rootdir

Hello i need to apply this configuration :

        - name: rootdir
          hostPath:
            path: /var/data
            type: Directory

I had to fetch the helm and install locally, possible to integrate this feature ?

Support Kubernetes 1.22 for ingress

The ingress API version got changed in Kubernetes 1.22.

Thus, all the charts don't work on Kubernetes >= 1.22 when ingress is enabled.

breaking changes from 1.x -> 2.x regarding PVC use not well documented (how to make it work on 2.x?)

After upgrading my standard PVC defined like this (in values.yaml):

persistence:
  data:
    enabled: true
    existingClaim: pvc-nfs-microserv-bt

stopped working (now simply /data is not custom-mounted), and I couldn't find out how to make it work under 2.x.

Any ideas?

Question -

Hi! Awesome to see you put this together! Quick question (might be a bit stupid since I'm not very good with k8s, ruby or huginn) but if you want to add more agents than the default by for example creating your own (https://github.com/huginn/huginn_agent). Then I assume you could just create your own image including those gem:s and then reinstall the chart. Correct? Or is there a better way?

So change this:

artifacthub.io/images: |
  - name: huginn/huginn
    image: docker.io/huginn/huginn-single-process:4d17829cf6b15b004ad3f4be196303dca4944810

To this:

artifacthub.io/images: |
  - name: huginn/huginn
    image: docker.io/victorbjorklund/custom-huginn:latest

RTnetlink answers: file exists

Hi. Apologies if this is answered elsewhere, but I've been stuck on this for a very long while and I really want to solve it. I have googled to no avail. I know the charts are deprecated but any comment helps.

This is how I install and configure the chart on my cluster:

helm install pine \
  --set env.LOCAL_NETWORK="10.0.0.0\/8\,172.16.0.0\/12\,192.168.1.0\/24" \
  --set env.OVERRIDE_DNS_1=8.8.8.8 \
  --set env.OVERRIDE_DNS_2=8.8.4.4 \
  --set env.OPENVPN_CONFIG=ca_vancouver \
  --set env.OPENVPN_OPTS="--inactive 3600 --ping 10 --ping-exit 60 --pull-filter ignore ping" \
  --set env.OPENVPN_PROVIDER=PIA \
  --set env.OPENVPN_USERNAME=... \
  --set env.TRANSMISSION_DOWNLOAD_DIR=\/media \
  --set env.TRANSMISSION_INCOMPLETE_DIR=\/media\/incomplete \
  --set secretEnv.OPENVPN_PASSWORD=... \
  --set persistence.existingClaim="nfs-pvc" \
  --kube-context=pine \
  -f values.yaml \
  utkuozdemir/transmission-openvpn

my values.yaml...

extraVolumeMounts:
  - mountPath: /media
    name: media

extraVolumes:
  - name: media
    persistentVolumeClaim:
      claimName: nfs-pvc

persistence:
  accessModes:
    - ReadWriteMany

This runs perfectly, but then once the kubelet evicts the pod (several days later, at random) and creates a new one, the pod creation Crashloops when trying to add routes with:

Setting OpenVPN credentials...
adding route to local network 192.168.1.0/24 via 10.42.1.1 dev eth0
RTNETLINK answers: File exists

Deleting the pod and then letting it restart solves the issue, but this shouldn't happen --this takes my transmission server down until I manually delete the crashlooping pod.

I have seen many explanations around:

• Some suggested to add all possible local networks under LOCAL_NETWORK (tried that, by using the three different CIDRs listed above, to no avail).
• Some suggested to add an explicit value for OPENVPN_CONFIG, set it to ca_vancouver, this also didn't fix the issue.
• The official docker image's documentation has an entry for this error; however, it's been left behind as a TODO item: https://haugene.github.io/docker-transmission-openvpn/faq/#rtnetlink_answers_file_exists

Please advise.

Unable to overwrite database.db file with updated password

If I deploy filebrowser using helm and set a password using config override and then re-deploy with a new password by using the configmap override, the password does not get updated in the database.db file stored in Azurefile. (I am aware about using the UI and CLI to change password, but was looking for some automated way)