design
kubevirt
Our great sponsors
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
design
-
Docker Without Docker
> we'd have been fighting cni complexity to make it work.
Appreciate the candid responses, thanks for taking the time. That ipv6 wireguard peering post was really fascinating I read that too. Wireguard has been quite the a game-changer in it's space as well and a lot of value IMO is just in the simplicity and difficulty of misconfiguration, even though the performance is also fantastic.
Grateful that ya'll are sharing what you're doing right/finding interesting.
Since ya'll might appreciate this, I think there's an ultimate form of all these orchestrators out there that boils everything down to the "operator pattern" -- I call it "buhzaar" but I tried to get my thoughts out of the notebook a while ago[0]. It's almost like a completely normalized DB might be -- to strip an orchestrator down to it's bare minimum, which facilitates other processes that do resource provisioning and management. Then let people bring their own things that provision resources (and maybe you some "officially supported" ones but they all live separately and iterate separately).
I didn't quite put down all the thoughts I had but you think this is too much normalization (in the same way no one wants to do 7 joins)? You could argue that both nomad and k8s are denormalized (they intrinsically "know" how to provision/manage certain things) to a certain extent, and nomad just "bundles" less.
[0]: https://gitlab.com/buhzaar/design
-
Mariadb and ZFS
Please feel free too, would love to chat about this. I think we think extremely similarly -- What you're trying to build is almost exactly what I'm trying to build, except I plan on getting my leverage from k8s (and eventually my own thing that I'm working on called buhzaar which aims to be simpler than k8s).
kubevirt
-
Kubernetes For The Sysadmin - Enter KubeVirt
First, download virtctl for ARM: https://github.com/kubevirt/kubevirt/releases/tag/v1.1.0-alpha.0
-
KubeVirt v1.0 has landed! This release demonstrates the accomplishments of the community and user adoption over the years
The full list of changes can be found in the Release notes. There are performance and scalability benchmarks published for the v1.0 release.
- What is the status of Red Hat Enterprise Virtualization and oVirt?
-
Proxmox, CEPH and kubernetes
If you're happy with k8s and longhorn, why add Proxmox as another layer underneath? Consider kubevirt ?
-
Kubernetes for temporary VM?
Have you looked at http://kubevirt.io/ ?
-
How does your company roll out code?
If the answer to "how do you run VMs" is "Kubernetes does it" then its about https://kubevirt.io/
-
Docker's deleting Open Source images and here's what you need to know
We are even using Docker Hub to store and distribute VM images...
https://github.com/kubevirt/kubevirt/blob/main/containerimag...
-
Blog: KWOK: Kubernetes WithOut Kubelet
Docker Desktop runs dockerd in a Linux VM with Apple's hypervisor framework. You can also run containers in a Linux VM with Parallels or VMware Fusion hypervisors. But you can't run VMs inside those VMs as it stands today. This works fine on Intel Macs which means you can't experiment and use KVM - one of the killer features of Linux and things like https://kubevirt.io/
-
Docker + portainer vs k8. EILI5
Proxmox VE can run VMs and LXC containers (see my comment below on LXC). Kubernetes can run OCI containers, but there's also KubeVirt for running VMs.
-
Live Switching Pods to another Node on Resource Limits
Another option would be something like KubeVirt but that is a different use case where you are actually running a VM in a container for hard-to-containerize workloads.