maintainersummitindia2024

A vital part of contributing to Kubernetes is testing. Reading existing tests lets you understand how a particular component works. You're also expected to write tests when making changes to the code base. The K8s codebase has different kinds of tests like unit, end to end and conformance tests. Given the scale of K8s, all of these are important to make sure that a feature works as intended and no edge cases come up when all the components are deployed in a production environment.

If you're getting started with contributing to K8s, learning the entire testing infrastructure can be overwhelming. This talk aims to give an introduction of the different types of tests in K8s and how you can setup your dev environment to run them locally. Along with unit tests, the talk also aims to give a demo of setting up tools like kubetest2 and hydrophone to run e2e and conformance tests with a kind cluster. After the talk you'll be ready to write your own tests for K8s and improve the test coverage.

Anyone working with Kubernetes knows how hard it is to put out a Kubernetes release. But actually, how are releases cut? This talk is for cloud-native practitioners who care about the environmental impact of their work. Focusing on insight into daily life, the tools, and the methodologies, the release engineers have a strong identity of the ecological consideration at every step.

We'll explore key aspects such as the automation tools that streamline the release process, the challenges of ensuring efficient resource usage, and the design principles that promote sustainability. Through practical demonstrations, we'll showcase best practices like optimizing CI/CD pipelines and leveraging containerization for minimal resource consumption. Participants will be equipped with actionable knowledge to enhance the sustainability of their Kubernetes releases. The key takeaway would be how the existing tools could be adapted and shared by more of the project, like image promoters.

Join us for an immersive workshop on LitmusChaos, the CNCF-incubating chaos engineering framework, as we share our journey toward graduation. We'll cover our transition from Litmus v2 to v3, security audits, new plugins, and our contributions to documentation and mentorship. This session will provide insights into building a globally impactful open-source project, especially for those in sandbox or incubating stages.

In the second half, we’ll guide you through installing Litmus, running your first chaos experiment, and connecting your ChaosHub. We’ll explore how to create custom experiments using the Litmus SDK, encouraging participants to suggest and test their own chaos scenarios. Bring Your Own Chaos (BYOC) and let’s execute it together in real time. Don’t miss this interactive deep dive into chaos engineering!

When it comes to packaging and distributing containerd, there’s always a confusion that arises from time to time: should we ship it ourselves or rely on vendors? While vendor distribution can be convenient, there can be surprising issues too. Another question arises: should we package other dependencies together with official release to ensure consistency? These considerations bring up a bigger discussion about best practices for distribution and packaging. We will be discussing perks and pitfalls of the different approaches to distributing core components in cloud native ecosystem like containerd and runc. Insights into how other projects handle their distribution could provide a valuable direction forward for the wider community. We also take a peek into the testing infrastructure that containerd uses to guarantee what we distribute is rock solid.