<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Chaos :: Tag :: Rejekts2026 and KubeCon EU 2026</title>
    <link>https://kubecon25.nicolai-ort.com/tags/chaos/index.html</link>
    <description></description>
    <generator>Hugo</generator>
    <language>en</language>
    <atom:link href="https://kubecon25.nicolai-ort.com/tags/chaos/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How Chaos-Engineering works: Implementing Failure Injection on Kubernetes with Rust</title>
      <link>https://kubecon25.nicolai-ort.com/day-2/07-chaosengineering/index.html</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      <guid>https://kubecon25.nicolai-ort.com/day-2/07-chaosengineering/index.html</guid>
      <description>Code/Demo A general introduction to chaos engineering with specificly showing implementations by Chaos Mesh and Litmus. After that the talk continues into the implementation of a custom chaos operator, written in rust.&#xA;Chaos Engineering Chaos Engineering is the discipline of experimenting on a system in order to build confidence in the systems capability to withstand turbulent conditions in production ~ Chaos Community (2015)&#xA;CNCF-Projects: Chaos Mesh, Litmus, Chaos Blade, Krkn Types: Pod Chaos (Delete/Terminate), Pod Network Chaos (Faults/Packet loss), Node Chaos, JVM Chaos, Infra Chaos(Reboot vms), … APIs Chaos Mesh: A Specific CRD per Chaos Type (PodChaos, NetworkChaos, …) Litmus: Chaos Engine Config that defines the type in it’s spec TODO: Steal sample CRDs</description>
    </item>
  </channel>
</rss>