Nick Maliwacki

I took a quick crack at allowing backends to be mutable, see https://github.com/KnicKnic/gobetween/commit/9a7d1915f3709f8b797e2adf21ddf65c18386513 Also I would like to comment that the kubernetes discovery ran into the same issue of backends...

There are two remaining issues. 1. starting a server with "static" discovery. The initial server.Start calls Discovery.Start , which does not push the backend immediately, and instead launches a go...

@rannaot another option would be to use Windows Server failover cluster. You could use gobetween.exe inside a "Generic Application" Resource. The only thing is you will have to copy gobetween.exe...

Builds on or https://github.com/yyyar/gobetween/pull/256/files

Updated Contributing.md Kept LICENSE.txt as github will detect that and mark the license for the repository

Another simple integration option go through kubernetes. Have the IPAM module or external software set either the svc.Spec.loadBalancerIP or some annotation that denotated externally leased IP. The only thing that...

> @KnicKnic That is already doable if I ubderstood6you correctly. You can already prevent metallb from allocating (still validating) and can set to svc.status.loadBalancerIP yourself and have that picked up...

The biggest issue I see is leasing, if we want to support any mechanism that has lease style mechanics like DHCP (which I would love to see accomplished in this...

> The thing is, 1. implies two sources of truths probably and threading. And the others (2 and 3) are too high level to see how they will work with...

I think that this is the responsibility of the application running in the container to guarantee that it's data is flushed. And that the volume should respect the application's flush...