Define Keptn Projects

Define what a project does

Tasks and sequences

Learn about tasks and sequences that define what your project does

A simple project

A simple project with dev, hardening, and production stages

Delivery sequence

Customize your delivery and staging process.

Quality Gates evaluations

Implement Quality Gate evaluations in your project

Delivery Assistant

Approval to control the delivery process

Remediation Sequence

Implement a remediation sequence

Deployment with Helm

Details about Keptn using Helm for deployment.

Triggers

Using triggers to kick off a sequence

Demo: Quality gate evaluation using metrics from another tool

How to use a tool to provide metrics for a quality gate evaluation

Orchestrate security checks

How Keptn can orchestrate security checks

Orchestrate Argo Rollouts from Keptn

How Keptn can orchestrate Argo Rollouts deployments

Orchestrate ArgoCD from Keptn

How Keptn can orchestrate ArgoCD deployments

This section provides information about the activities your Keptn project can do and how to implement them.

For information about the “mechanics” of working with Keptn projects, see Manage Keptn Projects.

Keptn is most frequently used as an orchestrator for delivery orchestration. You can orchestrate any sequence and leverage the built-in Keptn SLO validation. Keptn connects your tools and makes data-driven orchestration decisions without requiring you to do large amounts of custom coding..

This section provides information and samples to illustrate common practices with the following pages:

  • Tasks and sequences explains the components of the shipyard file that are populated to define what Keptn orchestrates.

  • A simple project illustrates the shipyard for a multi-stage project with dev, hardening or staging, and production stages that runs functional tests in the hardening stage, and performance tests in the hardening stage.

    This project uses the following capabilities:

  • Delivery sequence builds the shipyard for another multi-stage project but it utilizes the deployment strategies more extensively.

  • Quality Gates discusses how to set up a quality-gates stage that evaluates a deployment or release using metrics from the observability platform of your choice, based on criteria you define.

    This page also includes a short video that steps you through the implementation process for a quality gate evaluation.

  • Delivery Assistant illustrates how to implement a shipyard that has both manual and automatic delivery options, depending on the results of the quality gates evaluation.

Keptn can also be used to monitor your released software and software site and, if it finds problems, can be set up to “self heal” – in other words, to automatically take steps to remediate the problem. For example, it can scale your resources up or down or roll back the software to a previous release or send notifications to staff members.

Other examples of what you can do with Keptn: