Maybe I'm missing something, but thought you would have something to tie the pod to the pvc? In the pod definition it looked like it would go to pod-pvc, but the pvc you create was nginx-pvc? But very cool to see the simplicity of the microk8s and micro-ceph in a "virtual" world.
Hi Brendan, Great video! Although I do have 1 concern and that is combing MicroK8s & MicroCeph all on the single network, I built a K3S\Longhorn cluster and experience huge performance issue due to Longhorn replication and automatic snapshotting processes....how difficult would be to segregate the storage network from the MicroK8s pod and ingress network? Cheers
@64242359 hop over to the VHT forums here: www.virtualizationhowto.com/community create a topic under Kubernetes if you would like to discuss in more detail. Thank you for your comment!
The biggest advantage is footprint. full blown k8s (e.g. openshift) is heavy and requires a lot of resources to run and manage. Microk8s is nice and light, provides a great platform for just firing up local pods on a small footprint machine. It has an advantage over say minikube too because it allows you to have a multi node cluster, as shown in this video.
That depends on so many things... I personally started out 4 years ago running vanilla k8s. Building and destroying tens of clusters at home in my lab. Trying all sorts of things. It taught me so much! But now that I am more than fluent with kubernetes, I wish to spend my time on other things to learn. 2 months ago I made the choice to also move to microk8s and it's been a super smooth ride. I no longer have to think about maintaining my ansible roles for newer versions or new features. Upgrading my clusters. Basically everything. Another thing I really like is the resource usage. A completely idle kubernetes cluster built with kubeadm with only nginx and cilium cni would consume over 20% CPU usage in a 4 core VM on a modern system. Most of it by kube-api. My nodes running microk8s idle runs on less than 1% cpu utilisation and on top of that 1/5th of the memory consumption. 🙂 If you have the time and need to learn, then yes i recommend vanilla kubernetes. But if you don't need to learn, do yourself a favor and get a completely managed solution. I am very glad I did!
Regular CEPH runs on dockers containers inside a cluster of docker engines.. A little more bare metal than Kunernetes but a virtualized environnement none the less..;-)
Never heard of micro-ceph. I've worked with normal CEPH but this one is pretty darn easy and cool!
Thank you, it's very clear and the blog is great.
Thank you @fredericdiaz7656! Sign up for the forums as well here: www.virtualizationhowto.com/community
Me encantó tu video, genial!!! Muchas gracias, sigue creando contenido de ese nivel.
Maybe I'm missing something, but thought you would have something to tie the pod to the pvc? In the pod definition it looked like it would go to pod-pvc, but the pvc you create was nginx-pvc? But very cool to see the simplicity of the microk8s and micro-ceph in a "virtual" world.
Hi Brendan, Great video! Although I do have 1 concern and that is combing MicroK8s & MicroCeph all on the single network, I built a K3S\Longhorn cluster and experience huge performance issue due to Longhorn replication and automatic snapshotting processes....how difficult would be to segregate the storage network from the MicroK8s pod and ingress network? Cheers
can we mount microceph pool to a folder ?
Hi, thanx as always for these useful video, i'm wondering if is possible to use Openlens for a GUI.....
it's great but please explain why you do what you did., starting from, why microk8s and not regular k8s, pros and cons
@64242359 hop over to the VHT forums here: www.virtualizationhowto.com/community create a topic under Kubernetes if you would like to discuss in more detail. Thank you for your comment!
The biggest advantage is footprint. full blown k8s (e.g. openshift) is heavy and requires a lot of resources to run and manage.
Microk8s is nice and light, provides a great platform for just firing up local pods on a small footprint machine. It has an advantage over say minikube too because it allows you to have a multi node cluster, as shown in this video.
Perfecto
Longhorn was a nightmare compared to this and very buggy.
Why used micro8s?I think used home lab vanila k8s or k3s better
That depends on so many things... I personally started out 4 years ago running vanilla k8s. Building and destroying tens of clusters at home in my lab. Trying all sorts of things. It taught me so much! But now that I am more than fluent with kubernetes, I wish to spend my time on other things to learn.
2 months ago I made the choice to also move to microk8s and it's been a super smooth ride. I no longer have to think about maintaining my ansible roles for newer versions or new features. Upgrading my clusters. Basically everything.
Another thing I really like is the resource usage. A completely idle kubernetes cluster built with kubeadm with only nginx and cilium cni would consume over 20% CPU usage in a 4 core VM on a modern system. Most of it by kube-api. My nodes running microk8s idle runs on less than 1% cpu utilisation and on top of that 1/5th of the memory consumption. 🙂
If you have the time and need to learn, then yes i recommend vanilla kubernetes. But if you don't need to learn, do yourself a favor and get a completely managed solution. I am very glad I did!
A shame that microk8s insists on using snap.
it doesn't, you can install it from source too
@@DarkAwesome85 If nitpicking is your thing you should read it as "A shame that microk8s insists on only releasing binaries as snap packages"
It’s crazy that we can’t use apt.
"day-mons"... hehe
Running ceph on virtualized storage isn't a good idea. The performance will be terrible.
Regular CEPH runs on dockers containers inside a cluster of docker engines.. A little more bare metal than Kunernetes but a virtualized environnement none the less..;-)