Add new slides for run and diagram with fade-out transitions
This commit is contained in:
parent
af174eaa63
commit
09f01d409f
6 changed files with 6030 additions and 8763 deletions
37
pages/diagram.md
Normal file
37
pages/diagram.md
Normal file
|
|
@ -0,0 +1,37 @@
|
|||
---
|
||||
level: 2
|
||||
---
|
||||
|
||||
# MVK
|
||||
|
||||
|
||||
<div class="grid grid-cols-1">
|
||||
|
||||
```mermaid
|
||||
%%{init: {'theme': 'dark', 'themeVariables': { 'darkMode': true }}}%%
|
||||
flowchart LR
|
||||
root((MVK))
|
||||
PS[Persistent Storage]
|
||||
LH[Longhorn]
|
||||
ING[Ingress]
|
||||
TRA[Traefik]
|
||||
CM[cert-manager]
|
||||
ETCD[etcd]
|
||||
KA[keepalived]
|
||||
|
||||
root --> PS --> LH
|
||||
root --> ING --> TRA --> CM
|
||||
root --> ETCD --> KA
|
||||
|
||||
classDef default fill:transparent,color:#fff,stroke:#888
|
||||
```
|
||||
|
||||
</div>
|
||||
|
||||
<div v-click>
|
||||
|
||||
We have in the build so far etcd and keepalived
|
||||
|
||||
there is still no persistent volume management or ingress
|
||||
|
||||
</div>
|
||||
68
pages/run-slide.md
Normal file
68
pages/run-slide.md
Normal file
|
|
@ -0,0 +1,68 @@
|
|||
---
|
||||
level: 2
|
||||
---
|
||||
|
||||
# RUN
|
||||
|
||||
So what does `infctl` look like then ...
|
||||
|
||||
````md magic-move {lines: true}
|
||||
|
||||
```bash
|
||||
cd ~/projects
|
||||
git clone https://codeberg.org/headshed/infctl-cli.git
|
||||
```
|
||||
|
||||
```bash
|
||||
cd infctl-cli/vagrant/dev/ubuntu
|
||||
pwd
|
||||
/home/user/projects/infctl-cli/vagrant/dev/ubuntu
|
||||
```
|
||||
|
||||
```bash
|
||||
vagrant up
|
||||
Bringing machine 'vm1' up with 'virtualbox' provider...
|
||||
Bringing machine 'vm2' up with 'virtualbox' provider...
|
||||
Bringing machine 'vm3' up with 'virtualbox' provider...
|
||||
Bringing machine 'workstation' up with 'virtualbox' provider...
|
||||
==> vm1: Checking if box 'ubuntu/jammy64' version '20241002.0.0' is up to date...
|
||||
==> vm1: Clearing any previously set network interfaces...
|
||||
==> vm1: Available bridged network interfaces:
|
||||
1) wlp0s20f3
|
||||
2) docker0
|
||||
3) br-9ebcfa7b8ec0
|
||||
4) br-b036d14629a8
|
||||
5) veth9ae7cf3
|
||||
==> vm1: When choosing an interface, it is usually the one that is
|
||||
==> vm1: being used to connect to the internet.
|
||||
==> vm1:
|
||||
vm1: Which interface should the network bridge to?
|
||||
```
|
||||
|
||||
|
||||
|
||||
```bash
|
||||
cd ../../..
|
||||
export LOG_FORMAT=none
|
||||
export VAGRANT_BRIDGE=wlp0s20f3
|
||||
|
||||
infctl -f pipelines/dev/vagrant-k3s.json
|
||||
🔄 Running step: Create Vagrant nodes
|
||||
🐞 Running command: ./scripts/install_vagrant_nodes.sh
|
||||
|
||||
```
|
||||
|
||||
|
||||
|
||||
````
|
||||
<div v-click>
|
||||
|
||||
Here is a [Demo](http://ascii.headshed.dev/a/ISIOKVA1AmckG2muwOMUOG4z5)
|
||||
|
||||
</div>
|
||||
|
||||
<div v-click>
|
||||
|
||||
Lets [try again](http://ascii.headshed.dev/a/bUzNNojNjkxytfDT6cRqhSVwN)
|
||||
|
||||
</div>
|
||||
Loading…
Add table
Add a link
Reference in a new issue