<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Legacy :: Tag :: Rejekts2026 and KubeCon EU 2026</title>
    <link>https://kubecon25.nicolai-ort.com/tags/legacy/index.html</link>
    <description></description>
    <generator>Hugo</generator>
    <language>en</language>
    <atom:link href="https://kubecon25.nicolai-ort.com/tags/legacy/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>When Platform Engineers Lead FinOps: Driving Reliability and $20M in Savings</title>
      <link>https://kubecon25.nicolai-ort.com/day0/14_finops/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://kubecon25.nicolai-ort.com/day0/14_finops/index.html</guid>
      <description>Sched Link A case study from expedia about finops.&#xA;The Cost-Reliability disconnect Background: Modern Infrastructure is complex ans large (1000s of clusters, multi-region,…) with huge operational responsibilities (SLA, SLO, scalabiloity, …) Platform Team: REliability, Performance, Stability FinOps Team: Cloud Resources reduction, budget adherence, efficiency Problem: Conflicting goals and often organizationally seperated Blind cost optimzation can lead to unintentional stability/performance problems that can quickly spiral Blind stability optimizations quickly lead to large overhead/overprovisioning and huge costs Patterns Establish views &amp; Baselines: Unserstand cost per cluster/workload and utilization patterns Revisit legacy: Old configs like static sizing, huge buffers, … Embrace rearchitecture without fear: Consolidation, instance optimization, infra rededisn should all be on the table Views &amp; baselines General recommendations</description>
    </item>
  </channel>
</rss>