This episode introduces the Giant Swarm Conversations Podcast and will be an introduction to what follows over the next 3 months. We also cover NEWS 1, 2, 3.
Giant Conversations Episode #01
This episode introduces the Giant Swarm Conversations Podcast and will be an introduction to what follows over the next 3 months. We also cover NEWS 1, 2, 3.
This weeks jingle from Nikolai Rodionov
Hosted by:
Main topics
- Introduction to why Giant Swarm does a Podcast
- This will be a time limited experiment.
- We want to have conversations with interesting people.
- We want to cover the news of the week from our ecosystem.
- We want to make Giant Swarm more human and introduce everyone to Swarmies.
- We will try to pick new jingles every week and here is the first one you just listened to.
- General Community News
- General Giant Swarm News
News from #swarmalicious
- Linkerd offers a new model for stable releases - 2.15
- WeaveWorks is winding down but ControlPlane is back the flux projects by employing maintainers
- Recent post from Alexis Richardson states We now move the Weaveworks "company" into a wider "community".
- Crossplan Graduation to CNCF
- Running K8s in Production Hackernews Post
- A collegue found a new way for RegEx :)
- All-In Podcast on Open Source AI Models shrinking the value of models to 0
- Maxim Dounin is starting FreeNGINX as lots of people are still running it and it will be interesting how that develops with gateway-api in play.
- IBM Engineers Forked Vault calling it OpenBAO
- Angel from adidas is writing how they built their platform
News from Giant Swarm
- Oliver did predictions again
- Swarmies Traveling with Talks:
- Marcus Noble at Rejekts in Paris: From Fragile to Resilient: Validating Admission Policies Strengthen Kubernetes
- Łukasz Piątkowski at Rejekts in Paris: No GitOps Pain, No Platform gain: Day 2 Challenges of Managing Kubernetes Fleets with GitOps
- Marco Ebert: Ingress-Nginx and 2024 Plans
- Puja Abbassi: Building Resilient Developer Platforms: Strategies for Overcoming Challenges and Crafting Future-Proof Solutions
Bug of Week (from our Retrospectives)
tl;dr: We enabled Loki on leopard yesterday. It should send logs to an object store. That object store is internal, but Loki was (mis)configured to use their proxy. Their proxy refuses the connection as it's an internal target it can not resolve. Their proxy logs the access and as Loki retried it a lot, their proxy's log volume filled up to 100% which resulted in their whole proxy service breaking down.
Therefore several other services, including our login to leopard didn't work anymore.