5 ms·
> services have a static port and I just route to the port in the caddyfile Just so I understand - this means deploying a new service involves building a docke
by e12e 4y ago
> services have a static port and I just route to the port in the caddyfile
Just so I understand - this means deploying a new service involves building a docker image, deploy it, then manually update the caddyfile (ie manual ingress)?
> There's a couple ways to mount the volumes, which is annoying,
Fwiw this is annoying on multi-node docker swarm too - i even consider proper volume support to be one of the strongest arguments for considering k8s even for somewhat simple setups.
- ungawatkt 4y agoyeah, that's what I have now. I see the path to letting nomad deal with the addressing (rather than specifying static ports), but setting up a route in caddy for a new service would still be manual. I expect you could do some fancy scripting/go templating with the caddyfile and template block to make it spin up new routes more "automatically", but at that point I think you'd be better off seeing what Consul could do for you. Or traefik discovery with tags, I expect that could be convinced to work with Nomad, not that I've tried. (edit, seems like yes [0]) And I'd agree that the volume story isn't great compared to what I know of k8s. There's info out there for setting up NFS volumes, or something like portworx or ceph, but that's going beyond what I want to do for 1-3 pet nodes on a home server, I can deal with volumes staying bound to a node. [0] https://traefik.io/blog/traefik-proxy-fully-integrates-with-hashicorp-nomad/ https://traefik.io/blog/traefik-proxy-fully-integrates-with-...
- e12e 4y agoBeen using traefik with docker swarm for ingress - and it works. But doesn't exactly feel slick imnho :/