Kubernetes - Cannot run any recipe

  • Hi Team,
    I've tried to install Kubernetes using official plugin from the OMV plugin repo. Did my best to try to configure it:

    From this point I can access the kubernetes UI on port 8443 or I was able to do it yesterday. Still the issue I'm facing is whenever I want to add any recipe i got this error:

    500 - Internal Server Error

    An exception has been thrown during the rendering of a template ("The XPath query '//system/shares/sharedfolder[name='<MODIFY>']' does not return the requested number of 1 object(s).") in "manifest" at line 28.

    What I can do to fix it?

  • votdev

    Added the Label resolved
  • votdev

    Added the Label OMV 7.x
  • You need to replace everything named <MODIFY> with your custom settings.

    Thanks !
    should I use absolute paths or relative paths?

    Code
    {% set librarySharedFolderName = '<MODIFY>' %}
    {% set importSharedFolderName = '<MODIFY>' %}
    • Official Post

    should I use absolute paths or relative paths?

    Neither. You should use the shared folder name not path.

    omv 7.4.14-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.15 | compose 7.2.16 | k8s 7.3.1-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Neither. You should use the shared folder name not path.

    Sure, changed to my share details and put user and user group. It was added successfully. But then how can I access it?

    In pods I can see this:

    I tried to access it using my omv address with those port? I tired to use phone app but cannot connect to a service.


    In kubernetes web ui also i cannot find any mention of immich

    • Official Post

    192.168.0.1 is your ip address not your FQDN (fully qualified domain name).

    omv 7.4.14-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.15 | compose 7.2.16 | k8s 7.3.1-1 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Sorry for asking not smart questions...

    but in my case :

    what should i put inside android app connected to local network (assuming no dns changes were done)?

  • The test to check if fqdn name resolution is working is to ping/lookup the fqdn for the container/pod- (from a client) and it must return the ip of the omv server.


    So, if you deploy wetty the fqdn will be wetty.omvserver.something (obviously change/update the <omvserver.something> to match your system) - you should be able to ping wetty.omvserver.something and omvserver.something and both resolve to the same ip.


    There are a few ways to fix this if you can't ping/resolve the fqdn...

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!