Keptn. Data Driven DevOps Automation with Ketpn. Automating Service Level Indicators/Service Level Objectives based build validation with Keptn and Jenkins
Introduction
- Keptn Keptn not only orchestrates Continuous Deployment, but it also orchestrates Continuous or Automated Operations.
- Keptn provides automated SLI/SLO-based quality gates Introduction to Data Driven DevOps Automation. Keptn is a CNCF sandbox project and aims to automate delivery and operational processes using a data-driven approach. Keptn’s architecture solves a key problem with traditional automation tools where process and tool integrations are often hard coded or hard to maintain. Keptn uses an event-driven orchestrator with declarative process and tooling definitions that eliminate the need for any custom tool integration and make changing processes or tools a matter of changing a config file entry! At the core Keptn integrates with your observability platforms to automate SRE best practices such as SLO validation as part of your DevOps delivery and operations automation. Start automating your DevOps processes with Keptn to cover SLO-based Quality Gates, Performance & Chaos Test Automation, Event Driven Delivery as well as SRE-driven Auto-Remediation.
- Quick Start
- tutorials.keptn.sh 🌟
- dynatrace.com: What is keptn, how it works and how to get started!
- medium: Keptn 0.6.0 — My top 5 favorite improvements
- altoros.com: Automating Event-Based Continuous Delivery on Kubernetes with keptn
- medium: How we are redesigning our microservices deployment strategy Sharing the story of why we decided to adopt Keptn internally at Dynatrace and how we are making it happen
- Keptn Jenkins Shared Library integrates Jenkins and Keptn with just a couple of function calls.
- Jenkins Online Meetup Andreas Grabner from Dynatrace will talk about automating Service Level Indicators/Service Level Objectives based build validation with Keptn and Jenkins.
- In many organizations up to 80% of pipeline execution time is spent in manual build validation steps. How can we reduce that? One option is applying Google’s SRE (Site Reliability Engineering) practices by automating SLI (Service Level Indicators) & SLO (Service Level Objectives) based build validation. This method has proven to detect problematic issues in production and also allows us to automatically approve or reject builds being pushed through our pipelines.
- In this session you learn the basics of picking good SLIs & SLOs and how to extract them from your monitoring tools. After this session you will be able to start implementing this integration yourself with Jenkins. To give you a jump start you will be introduced to the open source project Keptn which provides automated SLI/SLO-based quality gates. Then we’ll talk about Keptn Jenkins Shared Library which integrates Jenkins and Keptn with just a couple of function calls.
- youtube: Level-Up your Jenkins-based Delivery with Keptn
- thenewstack.io: How Keptn Automatically Configures Prometheus Ecosystems
- github.com/keptn-sandbox/keptn-on-k3s: Tutorial: Keptn for Dynatrace Users in 5 Minutes 🌟 - Tutorial on keptnProject with argoproj for canary deployments using Dynatrace for SLO-based rollout control
- youtube: Tutorial - Keptn in a box
- dynatrace-perfclinics.github.io: Why Devs Love Dynatrace 🌟 Codelab explaining the benefits of automating SLO-based quality gates with keptnProject.
Keptn Videos
Click to expand!
Keptn Images
Click to expand!
