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

Revise MVK documentation: enhance CLI-centric explanations, clarify use cases, and expand introduction with personal experiences and tooling insights.

Browse source
This commit is contained in:
jon brookes 2025-10-17 16:45:11 +01:00
parent 3d027bd7f7
commit 460c84ac9b
6 changed files with 74 additions and 36 deletions
Download patch file Download diff file Expand all files Collapse all files

11
pages/uses03.md
View file

@ -1,6 +1,6 @@
# Minimal Viable Kubernetes
Use Cases ?
## Use Cases
### 🏠 Local development
@ -15,14 +15,9 @@ Use Cases ?
<!--
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.
In pipelines we can deploy production like environments allowing us to try out produciton configurations before going into live
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.
test and pre-prod environmetns can be entirely or in part ephemeral, cutting cost and proving infrastructure as code
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
-->