logo
Dates

Author


Conferences

Tags

Sort by:  

Authors: Srinivasan Parthasarathy, Shubham Chaudhary
2022-10-27

You have a principled process for releasing your Kubernetes app that involves load testing, benchmarking and validation of service-level objectives (SLOs). But, will your app perform well when your cluster is subject to compute, memory, i/o, or network stress? In this talk, we will explore a novel approach that combines chaos injection for probing weaknesses in your Kubernetes infrastructure, with load testing, benchmarking and performance validation with SLOs for your app. The core thrust of our approach will be flexibility combined with simplicity. Your app may be cluster-local or externally exposed, may implement an HTTP or a gRPC endpoint, may have been specified using built-in or custom Kubernetes resources, may use any type of horizontal or vertical autoscaling, may use any CD/GitOps process for deployment, and you may be interested in probing your cluster by injecting compute, memory, i/o, network, or any other types of chaos. Regardless of these variations, this talk will demonstrate a dead simple way to automatically launch the unified “chaos + performance validation" experiment whenever the app is updated, and automatically notify an event receiver with metrics and SLO validation results once the experiment is completed.
Authors: Andreas Grabner
2022-05-17

tldr - powered by Generative AI

The talk discusses how to make observability actionable with Prometheus and Keptn, using Service Level Objectives (SLOs) and automation to keep cloud native systems reliable and resilient.
  • Observability is necessary for making informed decisions about complex cloud native systems
  • Prometheus and other frameworks make it easier to obtain observability data
  • Service Level Objectives (SLOs) can be used to define the desired state of the system
  • Automation can be used to keep the system in the desired state based on observability data
  • Keptn is an observability-driven orchestration engine for cloud native apps that uses SLOs and automation to keep systems reliable and resilient
Authors: Andreas Grabner
2021-10-13

Moving to k8s doesn’t prevent anyone from bad architectural decisions leading to performance degradations, scalability issues or violating your SLOs in production. In fact – building smaller services running in pods connected through service meshes are even more vulnerable to bad architectural or implementation choices. To avoid any bad deployments, the CNCF project Keptn provides automated SLO-based Performance Analysis as part of your CD process. Keptn automatically detects architectural and deployment changes that have a negative impact to performance and scalability. It uses SLOs (Service Level Objectives) to ensure your services always meet your objectives. The Keptn team has also put out SLO best practices to identify well known performance patterns that have been identified over the years analyzing hundreds of distributed software architectures deployed on k8s. Join this session and learn what these patterns are and how Keptn helps you prevent them from entering production.