docs(day2): Added single talk notes
All checks were successful
Build latest image / build-container (push) Successful in 46s
All checks were successful
Build latest image / build-container (push) Successful in 46s
This commit is contained in:
parent
d2f3f5f95d
commit
4d528bf5de
38
content/day2/01_chance-of-kubernetes.md
Normal file
38
content/day2/01_chance-of-kubernetes.md
Normal file
@ -0,0 +1,38 @@
|
|||||||
|
---
|
||||||
|
title: "Cloudy with a chance of kubernetes"
|
||||||
|
weight: 1
|
||||||
|
tags:
|
||||||
|
- kubecon
|
||||||
|
- platform
|
||||||
|
---
|
||||||
|
|
||||||
|
<!-- {{% button href="https://youtu.be/rkteV6Mzjfs" style="warning" icon="video" %}}Watch talk on YouTube{{% /button %}} -->
|
||||||
|
<!-- {{% button href="https://docs.google.com/presentation/d/1nEK0CVC_yQgIDqwsdh-PRihB6dc9RyT-" style="tip" icon="person-chalkboard" %}}Slides{{% /button %}} -->
|
||||||
|
|
||||||
|
## Background
|
||||||
|
|
||||||
|
- Scale: 100s of clusters
|
||||||
|
- Cloud: Azure, AWS, GCP
|
||||||
|
- The baseline: Single AWS Region and applications on vms
|
||||||
|
- Goal: Operate on different locations
|
||||||
|
- History: They added more and more regions - 6 Providers in 6 Regions across 29 locations
|
||||||
|
- Problem: Different tooling across different cloud providers
|
||||||
|
- Idea: Kubernetes abstracts the specific cloud provider infra
|
||||||
|
|
||||||
|
## The way
|
||||||
|
|
||||||
|
- Idea: Use managed kubernetes
|
||||||
|
- Problem: In 2018 the managed offerings were in beta or very limited
|
||||||
|
- Challenge: Opinionated cloud specific stuff
|
||||||
|
|
||||||
|
### Iterations
|
||||||
|
|
||||||
|
1. Clusters based on vms created by terraform and other automation tools -> They realized that they need multiple clusters per region
|
||||||
|
2. Their own application delivery platform that deployed to the right clusters across regions for better DevEx
|
||||||
|
3. k8s on k8s (hosted cp) -> Current setup with a terraform managed parent cluster
|
||||||
|
4. Idea: Host the Partent-Cluster on managed kubernetes -> They need to abstract some things away
|
||||||
|
5. Solution: Use their good old aplication delivery platform
|
||||||
|
|
||||||
|
### Abstractions
|
||||||
|
|
||||||
|
- Use custom CRDs to abstract the same behaviour across providers
|
@ -5,7 +5,7 @@ weight: 6
|
|||||||
---
|
---
|
||||||
|
|
||||||
The second day of kubecon was my main "meeting day" this year - aka there were a bunch of scheduled meetings with manufacturers, partners, potential partners or just to get to know someone/a project.
|
The second day of kubecon was my main "meeting day" this year - aka there were a bunch of scheduled meetings with manufacturers, partners, potential partners or just to get to know someone/a project.
|
||||||
What does this mean for you? Another day with only a few sessions - the meeting notes are not available online.
|
What does this mean for you? Another day with only a few sessions (I only managed to attend two and only one was worthy of note taking) - the meeting notes are not available online.
|
||||||
|
|
||||||
In the evening we attended the "German Community Stammtisch".
|
In the evening we attended the "German Community Stammtisch".
|
||||||
|
|
||||||
@ -20,3 +20,9 @@ In the evening we attended the "German Community Stammtisch".
|
|||||||
- Portworx
|
- Portworx
|
||||||
- Fastly
|
- Fastly
|
||||||
- Syseleven
|
- Syseleven
|
||||||
|
- Netbird
|
||||||
|
- VMware
|
||||||
|
- Stackit
|
||||||
|
- Harness
|
||||||
|
- Mia Platform
|
||||||
|
- and many, many more...
|
Loading…
x
Reference in New Issue
Block a user