Hacker News Reader

Hey, yes! We're super interested in varying grades of seamlessness wrt container migration. What would your use case be? Is it OK to shut down the container and pause network connections before starting the container up on the other host and then unleashing them? Or would you be looking for full process freeze/thaw like with CRIU?

View on HN

Yes, full freeze of process with CRIU could be an option though not limited to that. Tcp network pausing/throttling as well.

Regarding backpressure I am talking about reactive streams, of which I am a fan of late, this would be better suited perhaps at the application level [0].

Regarding infra/pod level migrations, I am wondering if this would be something to implement at the kubernetes level , perhaps a new type of controller/service ? You could then perhaps use labels to identify throttling/freezing/thawing of pods during migration.

[0]: http://www.reactive-streams.org/

Reply on news.ycombinator.com