09f36dff16
- 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.
58 lines
No EOL
1.4 KiB
Markdown
58 lines
No EOL
1.4 KiB
Markdown
---
|
|
level: 2
|
|
---
|
|
|
|
# MVK for development
|
|
|
|
The **V** in MVK is for *viable*, so why is MVK viable for single 'dev' nodes ?
|
|
|
|
<div class="grid grid-cols-1">
|
|
|
|
```mermaid
|
|
%%{init: {'theme': 'dark', 'themeVariables': { 'darkMode': true }}}%%
|
|
flowchart LR
|
|
root((1-node))
|
|
PS[Persistent Storage]
|
|
LH[Local attached]
|
|
ING[Ingress]
|
|
TRA[Traefik]
|
|
MET[cert-manager]
|
|
ETCD[etcd]
|
|
|
|
root --> PS --> LH
|
|
root --> ING --> TRA
|
|
ING --> MET
|
|
root --> ETCD
|
|
|
|
classDef default fill:transparent,color:#fff,stroke:#888
|
|
```
|
|
|
|
</div>
|
|
|
|
<div v-click>
|
|
|
|
Locally attached storage - single node implementation
|
|
|
|
Ingress can represent that of prodution environmetns that use cert-manager
|
|
|
|
</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
|
|
|
|
--> |