headshed/n25
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Add Ingress and Storage test slides with Vagrant instructions

Browse source
This commit is contained in:
jon brookes 2025-08-27 10:54:58 +01:00
parent 09f01d409f
commit f3d077e3c4
19 changed files with 319 additions and 38 deletions
Download patch file Download diff file Expand all files Collapse all files

36
pages/intro-slide.md
View file

@ -1,22 +1,30 @@
# What is Minimal Viable Kubernetes?
# Minimal Viable Kubernetes?
MVK is kubernetes for the impatient and impeverished, and consists the following features
What is MVK ?
- ≥ **CLI** - Living in the terminal, uses [`infctl`](https://mvk.headshed.dev/guides/intro/) command line pipeline
- 🧑‍💻 **Startup Friendly** - Getting a functional stack quickly and simply
- 🤹 **Automated** - Focus on an infrastructure as code
- 🎥 **Repeatable** - Repeatable, re-useable and predictable.
- 📤 **Portable** - Kubernetes that can run anywhere
- 🛠 **Hackable** - Simple to modify, extend and prototype
<br>
<br>
≥ **CLI first** uses [`infctl`](https://mvk.headshed.dev/infctl/quick-start/)
🧑‍💻 **Startup Ready** functional simply
🤹 **Automated** infrastructure as code
🎥 **Repeatable** re-useable and predictable.
📤 **Portable** kubernetes that can run anywhere
🛠 **Hackable** simple to modify & extend
<div mt-20 v-click>
<!--
See a [Demo that goes terribly wrong](http://ascii.headshed.dev/a/f8S5WqD7OyCzkTcoPZhCSnefX?t=30)
We live in the command line, so MVK is CLI centric. It uses a very simple command line tool, `infctl` to marshal scripts and commands in a stop by step manner, similar to the way we right pipelines in the cloud.
Then see [one that goes right](http://ascii.headshed.dev/a/jSYcC7p4pbkMdf1B07rQOiIa0?t=01:30)
It is simple to get started, so that startups and the impatient can become productive with Kubernetes quickly, without having to rely on managed offerings and in order to self host easily.
</div>
Each pipeline use steps of code that are repeatable, idempotent and using infrastructure as code.
Kubernetes *can run anywhere* so MVK takes that principle and applies this to the self hosted approach making it possible to have the same setup on-prem and in the cloud
It is important to keep things simple so as to be understandable, maintainable and easy to change and extend to our own use cases
-->