-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FR] guide on how exactly to use with helm including example of PV setup #71
Comments
Update on this on what I've found out.
|
Still working using this very handy mediaserver operator. I thought I'd share my current setup and config for anyone else in the same situation I was in when trying the project.
Notes:
|
hey @colin-riddell, thank you so much for your considerations! Regarding the A possible workaround would be having a general nodeselector as a default and override it in the single resources. |
hey @kubealex - yeah keen to help poc that. I tried messing with the template and couldn't get it to work. I was editing
Couldn't get this to work. I'm not using helm though, so I'm basing this on the assumption that the CRD still uses these templating values under the hood when it's applied? (I couldn't see where else it would be configured). I also tried editing the |
Hey hey.
Maybe I'm just being thick, but I'm not sure I understand how exactly to properly set this up correctly with PV claims etc. Does every service need a PV? I found myself writing out a very lengthy helm config by hand and after several dozen attempts still don't have all the properties configured.
it's not clear to me if the media should be shared on a created PV or via some other means with NFS or both.
An example of how to do that would be useful. Thanks in advance.
Happy to be told where to go, though 😅
The text was updated successfully, but these errors were encountered: