linter run

content/day1/02_sometimes_lipstick_is_what_a_pig_needs.md

@@ -27,7 +27,7 @@ The main topic of this talk is: What interface do we choose for what capability.
 
 * Autonomy: external dependency (low) <->  self-service (high)
   * low: Ticket system -> But sometimes good for getting an expert
-  * high: Portal -> Nice, but somethimes we just need a 
+  * high: Portal -> Nice, but somethimes we just need a human contact
 * Contextual distance: stay in the same tool (low) <-> switch tools (high)
   * low: IDE plugin -> High potential friction if stuff goes wrong/complex (context switch needed)
   * high: Wiki or ticketing system

content/day1/03_beyond_platform_thinking.md

@@ -68,4 +68,4 @@ Presented by the implementers at Thoughtworks (TW).
 ## Q&A
 
 * Your teams are pretty autonomus -> What to do with more classic teams: Over a multi-year jurney every team settles on the ownership and selfservice approach
-* How to teams get access to stages: They just get temselves a stage namespace, attach to ingress and have fun (admission handles the rest)
+* How to teams get access to stages: They just get temselves a stage namespace, attach to ingress and have fun (admission handles the rest)

content/day1/04_user_friendsly_devplatform.md

@@ -9,16 +9,14 @@ tags:
 This talk was by a New York Times software developer.
 No real value
 
-
 ## Baseline
 
 * How do we build composable components
 * Workflow of a new service: Create/Onboard -> Develop -> Build/Test/deploy (CI/CD) -> Run (Runtime/Cloud) -> Route (Ingress)
 
-
 ## What do we need
 
 * User documentation
 * Adoption & Patnership
 * Platform as a Product
-* Customer feedback
+* Customer feedback

content/day1/05_multitennancy.md

@@ -34,7 +34,7 @@ Part of the Multitannancy Con presented by Adobe
 
 * Use a bunch of components deployed by platform Team (Ingress, CD/CD, Monitoring, ...)
 * Harmonized general Runtime (cloud agnostic): Codenamed Ethos -> OVer 300 Clusters
-* Both shared clusters (shared by namespace) and dedicated clusters 
+* Both shared clusters (shared by namespace) and dedicated clusters
 * Cluster config is a basic json with name, capacity, teams
 * Capacity Managment get's Monitored using Prometheus
 * Cluster Changes should be non-desruptive -> K8S-Shredder
@@ -42,4 +42,4 @@ Part of the Multitannancy Con presented by Adobe
 
 ## Conclusion
 
-* There is a balance between cost, customization, setup and security between single-tenant und multi-tenant
+* There is a balance between cost, customization, setup and security between single-tenant und multi-tenant

content/day1/09_serverless.md

@@ -39,4 +39,4 @@ weight: 9
 * Resulting needs
   * Cluster aaS (using crossplane - in this case using aws)
   * DBaaS (using crossplane - again usig pq on aws)
-  * App aaS
+  * App aaS

content/day1/10_lessons_learned_from_building_a_db_operator.md

@@ -31,4 +31,4 @@ Another talk as part of the Data On Kubernetes Day.
 ## Pitfalls
 
 * Storage: Agnostic, Topology aware, configureable and resizeable (can't be done with statefulset)
-* Networking: Cluster-internal (Pod to Pod/Service), External (Split horizon over multicluster)
+* Networking: Cluster-internal (Pod to Pod/Service), External (Split horizon over multicluster)

content/day2/02_ai_keynote.md

@@ -37,4 +37,4 @@ A podium discussion (somewhat scripted) lead by Pryanka
 * Anything else
   * Jeff: How do we bring our awesome tools (monitoring, logging, security) to the new AI world
   * Paige: Currently many people just use paid apis to abstract the infra, but we need this stuff selfhostable
-  * Tim: I don'T want to know about the hardware, the whole infra side should be done by the cloudnative teams to let ML-Engi to just be ML-Engi
+  * Tim: I don'T want to know about the hardware, the whole infra side should be done by the cloudnative teams to let ML-Engi to just be ML-Engine

content/day2/03_accelerating_ai_workloads.md

@@ -51,4 +51,4 @@ Kevin and Sanjay from NVIDIA
 
 * There are different KPIs: starvation, prioprity, occupanccy, fainrness
 * Challenge: What to choose (the multi-dimensional decision problemn)
-* Needed: A scheduler that can balance the dimensions
+* Needed: A scheduler that can balance the dimensions

content/day2/04_sponsored_ai_platform.md

@@ -22,4 +22,4 @@ Jorge Palma from Microsoft with a quick introduction.
   * Deployment
 * Simple CRD that decribes a model, infra and have fun
 * Creates inferance endpoint
-* Models are currently 10 (Hugginface, LLMA, etc)
+* Models are currently 10 (Hugginface, LLMA, etc)

content/day2/05_performance_sustainability.md

@@ -16,4 +16,4 @@ It was pretty scripted with prepared (sponsor specific) slides for each question
 * Smaller LLMs on cpu only is preyy cost efficient
 * Better scheduling by splitting into storage + cpu (prepare) and gpu (run) nodes to create a just-in-time flow
 * Software acceleration is cool, but we should use more specialized hardware and models to run on CPUs
-* We should be flexible regarding hardware, multi-cluster workloads and hybrig (onprem, burst to cloud) workloads
+* We should be flexible regarding hardware, multi-cluster workloads and hybrig (onprem, burst to cloud) workloads

content/day2/06_newsshow_ai_edition.md

@@ -27,9 +27,9 @@ PAtrick Ohly Joined for DRA
 
 * Kube is the seed for the AI infra plant
 * Kubeflow users wanted AI registries
-* LLM on the edge 
+* LLM on the edge
 * Opentelemetry bring semandtics
-* All of these tools form a symbiosis between 
+* All of these tools form a symbiosis between
 * Topics of discussions
 
 ### The working group AI
@@ -39,7 +39,7 @@ PAtrick Ohly Joined for DRA
 * The landscape "cloudnative and ai" is WIP and will be merged into the main CNCF landscape
 * The future focus will be on security and cost efficiency (with a hint of sustainability)
 
-### LFAI and CNCF 
+### LFAI and CNCF
 
 * The direcor of the AI foundation talks abouzt ai and cloudnative
-* They are looking forward to more colaboraion
+* They are looking forward to more colaboraion

content/day2/08_multicloud_saas.md

@@ -45,7 +45,6 @@ A talk by elastic.
 I won't copy the explanations of operators/controllers in this notes
 {{% /notice %}}
 
-
 * Many different controllers, including (but not limited to)
   * cluster controler: Register cluster to controller
   * Project controller: Schedule user's project to cluster
@@ -70,7 +69,7 @@ I won't copy the explanations of operators/controllers in this notes
 * Potential solutions: Replace etcd with the external db
 * Chosen solution:
   * The controllers don't use CRDs for storage, but they expose a webapi
-  * Reconciliation still now interacts with the external db and go channels (que) instead 
+  * Reconciliation still now interacts with the external db and go channels (que) instead
   * Then the CRs for the operators get created by the global controller
 
 ### Large scale

content/day2/09_safety_usability_auth.md

@@ -28,7 +28,7 @@ A talk by Google and Microsoft with the premise of bether auth in k8s.
 * Gateway Solution:
   * Gateway TLS secret ref includes a namespace
   * ReferenceGrant pretty mutch allows referencing from X (Gatway) to Y (Secret)
-* Limits: 
+* Limits:
   * Has to be implemented via controllers
   * The controllers still have readall - they just check if they are supposed to do this
 
@@ -85,4 +85,4 @@ A talk by Google and Microsoft with the premise of bether auth in k8s.
 ## Meanwhile
 
 * Prefer tools that support isolatiobn between controller and dataplane
-* Disable all non-needed features -> Especially scripting
+* Disable all non-needed features -> Especially scripting

content/day2/99_networking.md

@@ -12,7 +12,7 @@ Who have I talked to today, are there any follow-ups or learnings?
 
 ## Flux
 
-* We talked about automatic helm release updates (lessons learned from flux)[/lessons_learned/02_flux]
+* We talked about automatic helm release updates [lessons learned from flux](/lessons_learned/02_flux)
 
 ## Cloudfoundry/Paketo
 

content/day2/_index.md

@@ -8,4 +8,4 @@ Day two is also the official day one of KubeCon (Day one was just CloudNativeCon
 This is where all of the people joined (over 2000)
 
 The opening keynotes were a mix of talks and panel discussions.
-The main topic was - who could have guessed - AI and ML.
+The main topic was - who could have guessed - AI and ML.

content/day3/03_oss_business_value.md

@@ -80,4 +80,4 @@ The value should be rated even higher than the pure business value.
 
 ## Conclusion
 
-* Ther is significant unrealized valze in open source
+* Ther is significant unrealized valze in open source

content/day4/01_container_images.md

@@ -16,4 +16,4 @@ tags:
 
 * Degger as a CI solution
 * Multistage docker images with distroless -> Small image, small attack surcface
-* Language specific solutions (ki, jib)
+* Language specific solutions (ki, jib)

content/day4/03_operator.md

@@ -47,7 +47,6 @@ flowchart TD
     depply-->|Please install|kapp
 ```
 
-
 ```mermaid
 flowchart LR
     oa(operator author)-->ba(Bundle and att to catalog)

content/day4/06_global_operator.md

@@ -59,7 +59,7 @@ A talk by TikTok/ByteDace (duh) focussed on using central controllers instead of
 * The reconciler knows which cluster it is working on
 * The multi cluster management basicly just tets all of the cluster secrets and create a manager+controller for each cluster secret
 * Challenges: Network connectifiy
-* Solutions: 
+* Solutions:
   * Dynamic add/remove of clusters with go channels to prevent pod restarts
   * Connectivity health checks -> For loss the recreate manager get's triggered
 

content/day4/_index.md

@@ -4,4 +4,4 @@ title: Day 4
 weight: 4
 ---
 
-The last day with a limited sponsor expo (10:00-14:30) and a bunch of people on the move (not me)
+The last day with a limited sponsor expo (10:00-14:30) and a bunch of people on the move (not me)

content/lessons_learned/_index.md

@@ -4,4 +4,4 @@ title: Lessons Learned
 weight: 99
 ---
 
-Interesting lessons learned + tipps/tricks.
+Interesting lessons learned + tipps/tricks.