In this session we will know about keptn which is a growing an open source enterprise-grade control plane for cloud-native continuous delivery and automated operations.

1. Presented By:
Abhishek Dwivedi
Sr. Software Consultant
Keptn: A Cloud-native application
life-cycle orchestration

2. Lack of etiquette and manners is a huge turn off.
KnolX Etiquettes
Punctuality
Respect Knolx session timings, you
are requested not to join sessions
after a 5 minutes threshold post
the session start time.
Feedback
Make sure to submit a constructive
feedback for all sessions as it is
very helpful for the presenter.
Silent Mode
Keep your mobile devices in silent
mode, feel free to move out of
session in case you need to attend
an urgent call.
Avoid Disturbance
Avoid unwanted chit chat during
the session.

3. Our Agenda
01
01
02
02
What is Keptn ?
03
03
Features of Keptn
04
04 How Keptn works ?
Architecture of Keptn
05
05 Use cases of Keptn
Problems keptn tries to solve ?
07 Demo
06

4. What is Keptn?
● A control-plane for DevOps automation of cloud-native applications.
● Declarative approach to build scalable automation for delivery and operations.
● Keptn uses a simple, declarative approach that allows specifying DevOps automation
flows like delivery or operations automation without scripting all the details.
● Keptn separates the process defined by SREs from the actual tooling defined by
DevOps engineers and the information about the artifacts.

5. Keptn tries to solve 3 major problems of old delivery and release process.
● Problem 1
Too complex automation pipelines are too hard to maintain!
● Problem 2
Duplicated Pipeline Code hard to maintain, extend & optimize.
● Problem 3
Too much manual expert work on test execution & SLO Analysis
Problem Keptn tries to solve ?

7. Features of Keptn
❖ Automating
● Observability, dashboards & alerting
● SLO-driven multi-stage delivery
● Operations & remediation
● Easy to integrate with supporting tools
(Subscription based)
❖ Declarative, extensible and based on GitOps
❖ Provide clear separation of concerns
• Developers
• Define which artifact to use
• Want fast feedback on their code
• DevOps Engineers
• Define which tools to use
• Ensure tools are properly configured
• Site Reliability Engineers
• Define delivery processes
• Define operations workflows

8. Architecture of Keptn
● Reduce pipeline‘s complexity by letting keptn orchestrate declarative, data-driven delivery and
ops automation

9. How Keptn Works ?

12. Keptn shipyard - process versus tooling
1. Process & Environment definition
2. Transparent to tooling (Keptn’s Uniform)
3. Separation done via Cloud-Events

13. Use Cases of Keptn
Automating Observability, Dashboards & Alerting
Automating SLO-driven Multi-stage Delivery
Automating Operations by Closed-Loop Remediation

15. References
Keptn Official Site: https://keptn.sh/why-keptn/
GitHub repo: github.com/keptn/community/tree/main/branding

16. Thank You !
Get in touch with us:
E-mail: abhishek.dwivedi@knoldus.com
Web: www.knoldus.com/contact-us/