search

kubealex / k8s-mediaserver-operator

Repository for k8s Mediaserver Operator project
MIT License
569 stars 77 forks source link

[BR] unable to use NFS mount as per read me #61

Closed anothersmith closed 1 year ago

anothersmith commented 1 year ago

when adding NFS details to my-values.yaml the installation breaks

helm install -f my-values.yaml k8s-mediaserver ./helm-charts/k8s-mediaserver/

Error: INSTALLATION FAILED: YAML parse error on k8s-mediaserver/templates/jackett-resources.yml: error converting YAML to JSON: yaml: line 59: did not find expected key

my-values.yaml

general:
  storage:
    customVolume: true
  volumes:
    nfs:
      server: 192.168.0.5
      path: /opt/plexmedia/
plex:
  enabled: false

pods launch fine if overrides are omitted

anothersmith commented 1 year ago

might be worth noting this is on a fresh k3s pi cluster

kubealex commented 1 year ago

hi @anothersmith thank you for reporting this. The README was not coherent, the indentation of the 'volumes' node was wrong, it should be stored under general.storage. By the way, there's also no need to use any my-values file, as the operator uses the CR while you are installing it via helm.

Can you please try just working on the k8s-mediaserver.yml CR? Thank you!

KnightDoom commented 1 year ago

error converting YAML to JSON: yaml: line 59: did not find expected key.

Usually when this happens, it is a error in indentation somewhere below that line. Note that is not necessarily in the line value specified. I have had luck passing the whole values into ChatGPT to check for indentation errors! 👍