Wow.. that was an epic response :-D
HN user
thebsdbox
zerofree requires a filesystem, the example we talk about above is below the filesystem. Clonezilla is great, however we wanted to implement more "logic" into the provisioning process.
https://kube-vip.io/hybrid/services/ covers a bit of it, the idea is to be decoupled so any on-premises environment can throw together their own CCM that speaks to their local network or IPAM.
Howdy!
https://kube-vip.io does two things: - Control Plane HA w/BGP or ARP - Service Type: LoadBalancer w/BGP or ARP
It is similar to metallb but has a number of differences under the covers in how it works inside Kubernetes, it is cloud controller agnostic so as long as something attaches an IP to spec.IngressIP then kube-vip will advertise it. For edge deployments loadBalancers addresses can use the local DHCP for addresses etc..
The HA control plane and service type LB is all handled by https://kube-vip.io and is designed to be as transparent to the user as possible.
For clarity the Control plane High-Availability and Service type LoadBalancer is all provided by kube-vip.io out of the box. The goal is to provide as "close to cloud provider" environment as possible :-)
tl;dr
My script/code doesn’t work efficiently, I changed to a similar runtime and in summary noticed no real difference.
As part of a competition before the last DockerCon I managed to get a container down to 69B
Details: http://thebsdbox.co.uk/in-pursuit-of-a-tinier-binary-er/
Code: https://gist.github.com/thebsdbox/29e395299f89b52214b66269f5...
"Most of the processes do not need root access" - To create the VM network interfaces the vmnet_start_interface() in pci_virtio_net_vmnet.c function needs elevated privileges... how have you managed to get around not having to run xhyve as root just to have a virtual Nic?
Or alternatively use virtual hosts and have descriptive hostnames pointing to numerous web instances.