Revise personal experience section in slides.md for clarity and conciseness
This commit is contained in:
parent
5e79d7efb2
commit
563e6333dc
1 changed files with 11 additions and 14 deletions
25
slides.md
25
slides.md
|
|
@ -62,28 +62,24 @@ Welcome
|
||||||
|
|
||||||
this is an intro to MVK and why I made it ...
|
this is an intro to MVK and why I made it ...
|
||||||
|
|
||||||
My K8s exp
|
My exp
|
||||||
|
|
||||||
up to 17/18 I was working with Docker
|
over 20+ years Unix, Linux, Winodws, internet managed infructure
|
||||||
|
|
||||||
then Swarm, migrated to K8s
|
early linux Xen and KVM, vmware and hyper-v
|
||||||
|
|
||||||
AWS cloud and vmware on prem
|
from 14 moving into containers with docker
|
||||||
|
|
||||||
one week deploying self-hosted K8s with ansible
|
2017/18 Swarm, then rapidly to kubernetes
|
||||||
|
|
||||||
the next week on call 24X7 with k8s in the mix
|
AWS/cloud and vmware/on prem vms, self-hosted
|
||||||
|
|
||||||
|
one week deploying self-hosted K8s with kubeadm & ansible
|
||||||
|
|
||||||
|
the next week production, on call 24X7 with k8s in the mix
|
||||||
|
|
||||||
Since then, I worked on managed k8s in Azure and AWS, often with Terraform
|
Since then, I worked on managed k8s in Azure and AWS, often with Terraform
|
||||||
|
|
||||||
MVK uses k3s but could as well be
|
|
||||||
|
|
||||||
* k0s
|
|
||||||
* minik8s
|
|
||||||
* talos
|
|
||||||
|
|
||||||
I would like to move toward Talos but k3s for now
|
|
||||||
|
|
||||||
I wanted to
|
I wanted to
|
||||||
|
|
||||||
* use my own knowlege to deliver my own self managed k8s
|
* use my own knowlege to deliver my own self managed k8s
|
||||||
|
|
@ -94,6 +90,7 @@ I wanted to
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
-->
|
-->
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue