I am still struggling with item 2, but may have a solution.
First more background: I have a possible situation where I have several hundred hosts in my rancher environment, and around 6 NFS mounts. However, only a handful of my hosts actually need to access this NFS mount.
If I leave the default options, I’ll end up with 6 x 300 extra containers which I blatantly do not need.
Would the solution be to build my own docker-compose/rancher-compose file where I only make the one simple change of adding the following extra label to the convoy-nfs service?
io.rancher.scheduler.affinity:host_label=mylabelforthisservice
Leading me to ask: Would it be difficult to put this host_label into the answer file for the default Convoy-NFS catalog item?