SREDAY

Whether you are already working with SRE in your organization or thinking about implementing this methodology, you learn the best by doing, and doing is much more fun when playing. The SRE game provides a safe environment to start experimenting with SRE. In the game, you will be challenged to advise an organization on increasing its reliability. Like in real life, you should balance the quality of the system with the number of features you deliver. Of course, incidents occur, and your success depends on the decisions you made. We will start the workshop with a short keynote. The keynote introduces you to the core concepts of the SRE game and practical tips on getting started. After the keynote, we will play the SRE game. During the SRE game, you need to help a fictive organization increase the reliability of its systems without stopping to deliver new features. After the game, we will reflect on the teams' performance and explain the optimal strategy to help the fictive organization. We will close the session with a small prize ceremony providing the winning team and the runner-up a small prize.

Moving your application to containers can be daunting. Many organizations have struggled with the move to microservices and containerized workflows. We’ve been there, and now that we’ve found the light at the end of the tunnel, we want to share it!

Have you ever looked into multi region deployments on AWS whether to enhance user experience or ensure business continuity to name a few? Are you interested to hear about how to achieve repeatability of multi region deployments with AWS CI/CD and Terraform? If yes, this talk is for you.

This session will focus on lesson learnt from architecting and deploying (large) kubernetes clusters at production environments. The lessons are all real world, Ones that me and the customers have experienced. If I can "Save" one soul I have done my part :-)

Organizations are focusing on incidents more than ever but failing to leverage them to their full potential. But by framing incidents and post-incident reviews as customer empathy-building opportunities, we can facilitate more creative technical problem-solving, unlock improvements to your response process, and enable organizational agility that otherwise might have gone unnoticed. This workshop will deliver actionable methods to increase customer empathy before, during, and after an incident. Attendees will learn how reframing incidents and post-incident reviews around the customer inspires more creative problem-solving and drives superior experiences for customers; and how deeper relationships between responding groups creates organizational gold.

Developer happiness is a nearly exact reflection of how happy your code merge path is... when it's riddled with friction, this impacts dev experience as well. We'll dive into how to change this.

“CVE shock” is the state of total helplessness felt by a dev or security engineer facing the overwhelming list of CVEs returned by the vulnerability scanner. Sound familiar? We’ll unpack this and help you overcome it.

Like any other technology transformation, k8s adoption typically starts with small “pet projects”. One k8s cluster here, another one over there. If you don’t pay attention, you may end up like many organizations these days, something that spreads like wildfire: hundreds or thousands of k8s clusters, owned by different teams, spread across on-premises and in the cloud, some shared, some very isolated. When we start building application for k8s, we often lose sight of the larger picture on where it would be deployed and more over what the technical constraints of our targeted environment are. Sometimes, we even think that k8s is that magician that will make all our hardware constraints disappear. In reality, Kubernetes requires you to define quotas on nodes, namespaces, resource limits on our pods to make sure that your workload will be reliable. In case of heavy pressure, k8s will evict pods to remove pressure on your nodes, but eviction could have a significant impact on your end-users. How can we proactively test our settings and measure the impact of k8s events to our users? The simple answer to this question is chaos Engineering.

Policy often causes more harm than good, is slow to update, exemptions are harder still to manage, measuring compliance at scale is near on impossible. Throwing some curly braces at a problem is not the solution. How do we fix it?

Hands-on session on latest SRE tools from Grafana Labs

How do you deliver security and reliability on a network with thousands of servers with complete automation? We will use signed certificates with principals for SSH to automate the infrastructure with Ansible. It will scale SSH securely and reliably to automate thousand of servers using Ansible.

Reliability Engineering is more relevant daily, but there is a right way and a wrong way to approach it. The wrong way is manual tracking and validation. The right way is automation and single-source of truth. We designed this presentation to show how automation can make Teams' work self-managing.

Adopting and evolving technologies in an organisation is important and can offer significant advantages. However, translating these advantages into bottom-line benefits often comes from combining technical change with social change - we must not just change the technology, but also rewrite the rules governing how that technology is used. We are seeing growing thought leadership moving into this sociotechnical space: SRE, Data Mesh, DevOps and Platform Engineering are equally about the technology as they are about the rethinking of how teams are designed and organised. In this talk we hope to help you understand how to apply this sociotechnical thinking to your organisation, so you unlock the - often untapped - bottom-line benefits of technical change.

Have you started your Cloud-Native journey? Now that you’ve gotten past that first hurdle, I’m here to say there’s more to think about. I’ll talk about stumbling blocks that a masked enterprise called AsgharLabs had to deal with, and hopefully shed some light on things you haven’t thought about.

Improve application resilience with chaos testing by deliberately introducing faults that simulate real-world outages. Azure Chaos Studio is a fully managed chaos engineering experimentation platform for accelerating discovery of hard-to-find problems, from late-stage development through production.

Security is generally the compromise made in the interest of faster release cycles. This talk covers the story of three real-world security breaches and the DevSecOp failures behind them. Featuring vastly different environments, these stories highlight the commonalities in most security breaches.

Ordinary Linux kdump support shares state between host system and crashkernel via root disk. How do you dump if there's no disks at all, or root disk LUKS keys aren't sharable with the crashkernel ? We demo a setup that successfully crashdumps by HTTP PUT using only crashkernel cmdline arguments.

Impostor Syndrome affects most of the people working in IT. It affects also conference speakers. I will share with you my struggles in public speaking and how I fight the impostor syndrome at every conference. Hopefully helping you to fight impostor syndrome in your every day life.

The journey from zero to hero in the Observability field!

Secrets are something we need to implement to secure our apps/api communication, how can we handle secrets securely? This session will focus on secret definition, why it's important to rotate them and how to handle them in a secure way. This session is based on a real business case, and include a demo on how to implement such solution. The business case is related on automation of secrets used by external partners which previously needed human interaction to be rotate, with the content of this session humans need just to notify partners that there is a new secret.

There are many ways to make someone look good. As an SRE you can help your Dev and Ops colleagues with making sure their applications run reliably, perform well and don’t consume too much resources. Do this in a large environment, with many moving parts and you’ll be their hero. During this talk we’ll show you how you can leverage machine learning in Kubernetes based environments to achieve hero status with ease.

What is the most valuable outcome? This is the most important question to answer before starting an engineering metrics program. In this talk I discuss which dev team metrics matter most, the outcome they produce, and pitfalls to avoid when starting a metrics initiative.

Are you afraid of production Linux Kernel upgrades? Too risky? But what if I told you that it is more risky NOT to upgrade your kernel regularly? And what if I told you it is safer to deploy the Linux Kernel than any other software? This talk aims to demystify Linux Kernel releases !

Feature flags allow you to enable and disable code without changing or deploying any source code, as well as letting you selectively route traffic to certain users or a percentage of certain users, along with other great tricks. It’s powerful stuff … but when you combine it with observability (the ability to understand the inner workings of your complex systems and other unknown-unknowns), what you get is a supercharged, superpowered version of both. With observability and feature flags, you and your teams get deep technical and business insights in real time about how your code is working, what changed with your last deploy, and how changes are impacting different users, apps, or groups.

Come and explore the landscape of SRE as it is in 2023, with the new trends, techniques and tools on the horizon.

We know that developers are not all the same. But wait, they kind of are. This talk shares lessons learned from 20+ million developers to help SREs better engage with application developers.

You’ve saved the world (or at least your local dev environment) and are now eating some celebratory shawarma. Now what? The post-incident world often looks different to the one before. What next? We’ve heard of post-mortem documents and incident review meetings but are they successful? Did we figure out the root cause or just cure the effects? Have we made things more brittle in the process? Might we have to repeat the steps in a month or three? This talk will go over some case studies of incidents and their remediations to try to answer some of those questions, and also the hardest part: getting the ball rolling.

What is the most valuable outcome? This is the most important question to answer before starting an engineering metrics program. In this talk I discuss which dev team metrics matter most, the outcome they produce, and pitfalls to avoid when starting a metrics initiative.