n25/pages/diagram-3node.md

---
level: 2
---

# MVK for pre-production

The **V** in MVK is for *viable*, so why is MVK viable for 3 or more nodes ?

<div class="grid grid-cols-1">

<img src="/k8s-3.drawio.png">

</div>


<!--

why is MVK 'viable' ?

Out of the box K8s examples and some deployments are not useable without other externalities

* Persistent storage - often built in to managed kubernetes cloud platforms
* Ingress - is also provided by cloud providers, K8s does not natively have this
* ETCD is often offered as the 'management plane', again as part of managed kubernetes by cloud providers

K3s does not use k8s traditional 3 node ETCD unless you configure it to do so

MKK's infctl pipelines configure 3 node k3s on all 3 nodes

it also adds Longhorn for persistent storage

ingress is impossible without metallb and some kind of load balancer - traefik being my preference but others could be used, of course

-->
Add new slides for run and diagram with fade-out transitions 2025-08-26 10:07:47 +01:00			`---`
			`level: 2`
			`---`

added gcloud intro - Created a new script `instalL_asciinema.sh` to automate the installation of asciinema. - The script detects the operating system and architecture to download the appropriate binary. - Supports Linux (both musl and GNU) and macOS (Darwin). - Sets executable permissions for the downloaded binary and verifies the installation by displaying the version. 2025-10-16 10:05:51 +01:00			`# MVK for pre-production`
Add new slides for run and diagram with fade-out transitions 2025-08-26 10:07:47 +01:00
added gcloud intro - Created a new script `instalL_asciinema.sh` to automate the installation of asciinema. - The script detects the operating system and architecture to download the appropriate binary. - Supports Linux (both musl and GNU) and macOS (Darwin). - Sets executable permissions for the downloaded binary and verifies the installation by displaying the version. 2025-10-16 10:05:51 +01:00			`The V in MVK is for viable, so why is MVK viable for 3 or more nodes ?`
Add new slides for run and diagram with fade-out transitions 2025-08-26 10:07:47 +01:00
			`<div class="grid grid-cols-1">`

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. 2025-10-21 15:47:15 +01:00			`<img src="/k8s-3.drawio.png">`
Add new slides for run and diagram with fade-out transitions 2025-08-26 10:07:47 +01:00
			`</div>`

Add Ingress and Storage test slides with Vagrant instructions 2025-08-27 10:54:58 +01:00
			`<!--`

			`why is MVK 'viable' ?`

			`Out of the box K8s examples and some deployments are not useable without other externalities`

			`* Persistent storage - often built in to managed kubernetes cloud platforms`
			`* Ingress - is also provided by cloud providers, K8s does not natively have this`
			`* ETCD is often offered as the 'management plane', again as part of managed kubernetes by cloud providers`

			`K3s does not use k8s traditional 3 node ETCD unless you configure it to do so`

			`MKK's infctl pipelines configure 3 node k3s on all 3 nodes`

			`it also adds Longhorn for persistent storage`

			`ingress is impossible without metallb and some kind of load balancer - traefik being my preference but others could be used, of course`

			`-->`