Source: medium.com
Closed-loop Remediation with custom IntegrationsCategory: Deployment, Kubernetes, Architecture, automation
Keptn 0.7 lifts the automation of remediation workflows and the integration of custom remediation providers (aka. action providers) to the next level. A level where you can configure multiple remediation actions per problem type and the effect of each remediation action is validated based on the SLO/SLI validation Keptn offers.
Additionally, the event-based architecture of Keptn allows plugging in custom action providers to integrate the automation tool of your choice. Automating remediation workflows comes into play when you want to automatically react to a problem in order to keep a microservice online and to avoid any user impact. Although the goal is clear, multiple challenges occur in this regard: You should use Keptn for automating remediation tasks since: Before exploring the Keptn 0.7 enhancements for the use-case of operation automation, three underlying core principles are highlighted and then used to explain the new features.
Additionally, the event-based architecture of Keptn allows plugging in custom action providers to integrate the automation tool of your choice. Automating remediation workflows comes into play when you want to automatically react to a problem in order to keep a microservice online and to avoid any user impact. Although the goal is clear, multiple challenges occur in this regard: You should use Keptn for automating remediation tasks since: Before exploring the Keptn 0.7 enhancements for the use-case of operation automation, three underlying core principles are highlighted and then used to explain the new features.
Related Articles
Community Partners
DevOps Careers