4 ms·
Does this fit in with hyperkube in some way? Can you see 'pods' that are really complete VM's which may or may not include OCI containers on them. For instance
by tmzt 10y ago
Does this fit in with hyperkube in some way? Can you see 'pods' that are really complete VM's which may or may not include OCI containers on them.
For instance, would a complete Windows Server instance fit the Pet Set concept in the scheduler?
- 101km 10y agoNothing to do with hyperkube. PetSets are simply ordinally ordered container collections instead of randomly ordered. The usual concept in Kubernetes is that a container has a name like 'thing-randomsuffix4242'. It is pushing you towards making your pods stateless and not precious so the failure handing logic is simple. If it is blown away for whatever reason can easily be replaced by the scheduler and 'thing-randomsuffix242b' is never far away. With a predictable ordering you can actually make assumptions you otherwise couldn't. For example, perhaps you want the convention that 'thing-predictable1' is the master and 'thing-rpredictable{2,3}' are the slaves.
- sandGorgon 10y agohyperkube is just a repackaging of all the different packages of k8s as a single binary. so rather than 'kubectl -v', you will run 'hyperkube kubectl -v'
- tmzt 10y agoCloser to minikube then? That was not at all clear to me from reading the site, where it seemed to be discussing a kubelet on an OS on bare metal or hypervisor, but not managing containers.