Add Ingress and Storage test slides with Vagrant instructions
This commit is contained in:
parent
09f01d409f
commit
f3d077e3c4
19 changed files with 319 additions and 38 deletions
|
|
@ -4,6 +4,7 @@ level: 2
|
|||
|
||||
# MVK
|
||||
|
||||
The **V** in MVK is for *viable*, so why is MVK viable ?
|
||||
|
||||
<div class="grid grid-cols-1">
|
||||
|
||||
|
|
@ -15,12 +16,12 @@ flowchart LR
|
|||
LH[Longhorn]
|
||||
ING[Ingress]
|
||||
TRA[Traefik]
|
||||
CM[cert-manager]
|
||||
MET[Metallb]
|
||||
ETCD[etcd]
|
||||
KA[keepalived]
|
||||
|
||||
root --> PS --> LH
|
||||
root --> ING --> TRA --> CM
|
||||
root --> ING --> TRA --> MET
|
||||
root --> ETCD --> KA
|
||||
|
||||
classDef default fill:transparent,color:#fff,stroke:#888
|
||||
|
|
@ -35,3 +36,23 @@ We have in the build so far etcd and keepalived
|
|||
there is still no persistent volume management or ingress
|
||||
|
||||
</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
|
||||
|
||||
-->
|
||||
Loading…
Add table
Add a link
Reference in a new issue