new round of day 2 + lessons learned

content/day2/07_is_your_image_distroless.md

@@ -0,0 +1,6 @@
+---
+title: Is your image really distroless?
+weight:7
+---
+
+Laurent Goderre from Docker

content/day2/99_networking.md

@@ -0,0 +1,29 @@
+---
+title: Networking
+weight: 99
+---
+
+Who have I talked to today, are there any follow-ups or learnings?
+
+## Operator Framework
+
+* We talked about the operator lifecycle manager
+* They shared the roadmap and the new release 1.0 will bring support for Operator Bundle loading from any oci source (no more public-registry enforcement)
+
+## Flux
+
+* We talked about automatic helm release updates (lessons learned from flux)[/lessons_learned/02_flux]
+
+## Cloudfoundry/Paketo
+
+* We mostly had some smalltalk
+* There will be a cloudfoundry day in Karlsruhe in October, they'd be happy to have us ther
+* The whole KORFI (Cloudfoundry on Kubernetes) Project is still going strong, but no release canidate yet (or in the near future)
+
+## Traefik
+
+{{% notice style="note" %}}
+They will follow up
+{{% /notice %}}
+
+* We mostly talked about traefik hub as an API-portal

content/lessons_learned/02_flux.md

@@ -0,0 +1,13 @@
+---
+title: Flux
+weight: 2
+---
+
+Some lessonslearned from flux talsk and from talking to the flux team.
+
+## Helm Autupdate
+
+* 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)