Typos and missing info

content/_index.md

@@ -7,6 +7,10 @@ All about the things I did and sessions I attended at KubeCon/CloudNativeCon 202
 
 This current version is probably full of typos - will fix later.
 
+## How did I get there?
+
+I attended KubeCon + CloudNAtiveCon Europe 2024 as the one and only [ODIT.Services](https://odit.services) representative.
+
 ## Style Guide
 
 The basic structure is as follows: `day/event-or-session`.

content/day2/99_networking.md

@@ -51,8 +51,23 @@ I should follow up
 ## Renovate
 
 * The paid renovate offering now includes build failure estimation
-* I was told not to buy it after telling the technical guy that we just use build pipelines as MR verification 
+* I was told not to buy it after telling the technical guy that we just use build pipelines as MR verification
 
 ### Certmanager
 
 * The best swag (judged by coolness points)
+
+### Upwind
+
+{{% notice style="note" %}}
+They will follow up with a quick demo
+{{% /notice %}}
+
+* A kubernetes security/runtime security solution with pretty nice looking urgency filters
+* Includes eBPF to see what code actually runs
+* I'll witness a demo in early/mid april
+
+### Isovalent
+
+* Dinner (very tasty)
+* Cilium still sounds like the way to go in regards to CNIs

content/day3/99_networking.md

@@ -7,4 +7,4 @@ Who have I talked to today, are there any follow-ups or learnings?
 
 ## VMware
 
-* Custoemr/partner dinner
+* Dinner

content/day4/99_networking.md

@@ -25,10 +25,13 @@ They will follow up with a quick demo
 
 ## Rancher/Suse
 
-* I just got some swag, Maik got a demo focussing on runtime security
+* I just got some swag, a friend of mine got a demo focussing on runtime security
 
 ## Kong
 
 * They didn't have any Insomina stickers and the insomnia guy apparently already left
 
-## Planetscale
+## Planetscale
+
+* Said hi and talked a bit about the future of vitess
+* Got some vitess stickers

content/lessons_learned/01_operators.md

@@ -8,4 +8,4 @@ title: Operators
 
 ## Work queue
 
-* Go channels as queues
+* Go channels as queues with priority support

content/lessons_learned/02_flux.md

@@ -10,4 +10,4 @@ Some lessonslearned from flux talsk and from talking to the flux team.
 * Currently you can just use the normal image autoupdate machanism
   * Requirement: The helm chart is stored as a OCI-Artifact
   * How: Just create the usual CRs and annotations
-* They are also working on generalizing the autoupdate Process to fitt all OCI articacts (comming soon)
+* They are also working on generalizing the autoupdate Process to fitt all OCI articacts (comming soon)