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">

```mermaid
%%{init: {'theme': 'dark', 'themeVariables': { 'darkMode': true }}}%%
flowchart LR
    root((3-node))
    PS[Persistent Storage]
    LH[Longhorn]
    ING[Ingress]
    TRA[Traefik]
    MET[cert-manager]
    ETCD[etcd]
    KA[keepalived]
    
    root --> PS --> LH
    root --> ING --> TRA
    ING --> MET
    root --> ETCD --> KA
    
    classDef default fill:transparent,color:#fff,stroke:#888
```

</div>

<div v-click>

close to production - storage and multi node 

</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

-->