1) Can you say more what you're looking for? Specifically image checkpoint/restore? Something else? 2) Yes! We're hiring :) However, you can start working on k8s wherever you are - we're 100% open source.

Disclosure: I work at Google on Kubernetes.

Suspect the parent may be talking about CRIU support? I think it's a way off, but it is definitely worth thinking about how this would work in Kube world.

I blogged about this here:

https://zwischenzugs.wordpress.com/2015/10/11/docker-migrati...

Is the open source work on Kubernetes at Google being done directly on the GitHub repo or is there an internal mirror where work is first done and internal issues tracked separately, similar to Android?

100% open (there is no mirror repo that I'm aware of). There's certainly internal discussion, particularly when some members of the team don't want to be "seen in public", but this isn't like other projects where it's sync'ed from a hidden internal repo.

Disclaimer: while I work at Google on Cloud, and know the K8s folks, I've never even committed any changes.

100% on GH and open. Some design talks might get hashed out in private, but they all end up in a GH issue or PR as a design doc.

I work at Red Hat on Kube.

It doesn't support checkpoints or container migrations right now, but it does go out of its way to hide from pods all the details about the host, in order to support them in a future release.