bsdpot/nomad-pot-driver#55 adding aliases as pot driver attribute#56
bsdpot/nomad-pot-driver#55 adding aliases as pot driver attribute#56einsiedlerkrebs wants to merge 1 commit intobsdpot:masterfrom
Conversation
|
Hm, this sounds like it won't scale well, unfortunately. Like, what do you do if you run 5 or 10 instances of the same services? I owe you an answer to the networking issues you had in that already closed task. Let me address this asap. |
than it won't work. But if you have only one it does. If you have multiple instances of the same service you probably have them on different machines. This is where the port forward approach is working. This here tries to be a more elegant way for localhost tunnels. |
|
And since its done with name resolution no changes to the pots internal address request need to be done, if this service should be announced differently e.g. via DNS round robin. |
|
I finally described most of our setup to you in #53
Not necessarily, running multiple instances of the same service also happens on the same host when doing deployments. The way we do this using nomad is:
After we started the deployment, all of these steps run automatically, orchestrated by nomad. This way we accomplish zero downtime updates in our cluster and in case a new version never stabilizes, the payload simply stays on the old version (typical example is that a new version requires more configuration or new resources). See here for the general concept: https://developer.hashicorp.com/nomad/tutorials/job-updates/job-rolling-update |
|
This sound mighty and useful! Not what I am looking for, yet! But I will read on. |
referes to #55