Revise MVK documentation: replace mermaid diagrams with images, add new sections for single node and three node viability, and enhance the usage slide with additional context.

This commit is contained in:
jon brookes 2025-10-21 15:47:15 +01:00
parent 563e6333dc
commit 072e2998ae
12 changed files with 212 additions and 77 deletions

View file

@ -58,33 +58,21 @@ Jon Brookes 2025
<!--
Welcome
why and why now ?
this is an intro to MVK and why I made it ...
I created it because
My exp
* was building a minimal k8s for our own hosting
* asked for an intro for techs getting into k8s
over 20+ years Unix, Linux, Winodws, internet managed infructure
as I've been working with unix, linux and systems since before Y2K and k8s since 2018 I thought I could have something to say
early linux Xen and KVM, vmware and hyper-v
from 14 moving into containers with docker
2017/18 Swarm, then rapidly to kubernetes
AWS/cloud and vmware/on prem vms, self-hosted
one week deploying self-hosted K8s with kubeadm & ansible
the next week production, on call 24X7 with k8s in the mix
Since then, I worked on managed k8s in Azure and AWS, often with Terraform
I wanted to
so I wanted to
* use my own knowlege to deliver my own self managed k8s
* bring down the cost of k8s
* share what I know and pass it on
* pass on what I have learnt
* not pay vercel
@ -93,6 +81,14 @@ I wanted to
-->
---
layout: image-left
image: why.jpg
transition: fade-out
src: ./pages/why.md
---
---
layout: image-right
image: cont3_c.jpg
@ -192,25 +188,30 @@ transition: fade-out
src: ./pages/usage-slide.md
---
---
transition: fade-out
src: ./pages/diagram-single-node.md
src: ./pages/out-the-box-node.md
---
---
transition: fade-out
src: ./pages/diagram-3node.md
src: ./pages/make-it-work.md
---
---
transition: fade-out
src: ./pages/gcloud-single.md
---
---
transition: fade-out
src: ./pages/three-node-happy.md
---
@ -221,8 +222,10 @@ transition: fade-out
src: ./pages/infctl-summary.md
---
---
transition: fade-out
src: ./pages/infctl-summary-end.md
---
---
layout: center