Slidedeck from Vienna DevOps & Security Meetup. This talk is keptn - an open source event driven control plane for continuous delivery and automated operations for kubernetes
WSO2Con2024 - WSO2's IAM Vision: Identity-Led Digital Transformation
Continuous Delivery and Automated Operations on k8s with keptn
1. What is
Andreas Grabner, Dynatrace
@grabnerandi
@keptnProject
https://keptn.sh
https://github.com/keptn
2. Confidential 2
That is why we are building
Because cloud native delivery and operations is a BIG challenge for enterprises!
Cloud Native
3. Confidential 3
MTTI
Mean Time to Innovation
MTTR
Mean Time to Remediate
4.8 days
4 hours
~ 10min
12.5 days 2 days ~ 1 hour
The reality and evidence supports
it!
https://dynatrace.ai/acsurvey
Only < 5% is „Cloud Native“
4. Confidential 4
Quote: “Pipelines seem to be becoming our new future un-managable legacy code!“
First: solves the Continuous Delivery Problem!
5. Confidential 5
Quote: “We spend more time in manual communicaton than remediating issues“
Second: has Continuous Operations at its Core!
ENGAGE TRIAGE FIND & ASSEMBLE RESOLVE RESTORE
MANUAL
COMMUNICATION
MANUAL
COMM
Before
After
RESTORERESOLVE
NUMBER
OF ISSUES CURRENT STATE: mostly manual
DESIRED STATE: mostly automated
6. 6
To Sum Up: Why we are building Keptn
Continuous Delivery - and even more Continuous Operations - is an area where many
enterprise struggle to implement proper solutions. Many approaches today are
brittle, error-prone and hard to maintain
Most approaches today
7. 8
Mission Control
“Automated Operations” = Day 2 Ops
Launch Control
“Continuous Deployment” = Day 1 Ops
Keptn is a Control Plane for Automate Delivery and Operations
Event-driven runbook automation
Productionproblemscan beautomaticallyremediatedin
real-timebyexecutingrunbooksthatrequirenomanual
intervention.
Self-healing blue/green deployments
Deploymentsthatfollowthe“Operationsas Code”
paradigmautomaticallyremediateproblemsandget
yourdeploymentpipelineworkingagain inundera
minute.
Automated multistage unbreakable delivery
pipelines
GitOps-enableddeliverypipelineswithautomated
qualitygates supportautomatedtestingandmonitoring-
as-a-service.
Declarative Delivery (Shipyard) Declarative Tooling (Uniform) Declarative SLI / SLO / SLA
9. 10
Config ChatOps IT Autom
Deploy Test Observe
One-Line Installation: $ keptn install
10. 11
Config ChatOps IT Autom
Deploy Test Observe
Zero-Touch Toolchain Integration: $ keptn wear uniform uniform.yaml
11. 12
Config ChatOps IT Autom
Deploy Test Observe
Re-Think Pipelines: $ keptn create project keptn-sample shipyard.yaml
S
T
A
G
I
N
G
P
R
O
D
DirectUpdateC D
Blue/GreenUpdateC D
12. 13
Config ChatOps IT Autom
Deploy Test Observe
Zero-Touch Cloud Native Services: $ keptn onboard service myservice [xxx.yaml]
S
T
A
G
I
N
G
P
R
O
D
DirectUpdateC D
Blue/GreenUpdateC D
PLACEHOLDER
PLACEHOLDER
13. 14
Config ChatOps IT Autom
Deploy Test Observe
Automated Multi-Stage Delivery: $ keptn new artifact myservice:1.0.0
S
T
A
G
I
N
G
P
R
O
D
ScoreDirect PerformanceUpdate Promote?C D T O
ScoreBlue/GreenUpdate Keep?C D T O
PLACEHOLDER
PLACEHOLDER
1.0.0
1 1 90
/
100
1.0.0
1 1 1 75
/
100
P
R
O
M
O
T
E
K
E
E
P
14. 15
A Quick word on Pitometer: Automated Deployment Validation
Metric Source &
Query
Grading Details
& Metric Score
Pitometer Specfile
Total Scoring
Objectives
2GB
Allocated Bytes (from Prometheus)
> 2GB: 0 Points
< 2GB: 20 Points
5%
2% < 2%: 0 Points
< 5%: 10 Points
> 5%: 20 Points
Conversion Rate (Dynatrace)
GraderSource
If value: 3GB
Score: 0
If value: 3.9%
Score: 10
Total Score: 10
15. 16
Config ChatOps IT Autom
Deploy Test Observe
Automated Quality Gates: $ keptn new artifact myservice:2.0.0
S
T
A
G
I
N
G
P
R
O
D
ScoreDirect PerformanceUpdate Promote?C D T O
ScoreBlue/GreenUpdate Keep?C D T O
1.0.0
1 1 45
/
100
1.0.0
1 1 1
2.0.0
2 2
A
B
O
R
T
16. 17
Config ChatOps IT Autom
Deploy Test Observe
Self-Healing Blue/Green Deployments: $ keptn new artifact myservice:3.0.0
S
T
A
G
I
N
G
P
R
O
D
ScoreDirect PerformanceUpdate Promote?C D T O
ScoreBlue/GreenUpdate Keep?C D T O
1.0.0
1 1 85
/
100
1.0.0
1 1 1
2.0.0
2 2
3.0.0
3 3
3.0.0
3 3 3
80
/
100
P
R
O
M
O
T
E
R
E
V
E
R
T
17. 18
Config ChatOps IT Autom
Deploy Test Observe
Zero-Touch Toolchain Updates: $ keptn update uniform <+neo,+end2end,+spinnaker>
S
T
A
G
I
N
G
P
R
O
D
ScoreDirect PerformanceUpdate Promote?C D T O
ScoreBlue/GreenUpdate Keep?C D O
1.0.0
1 1
1.0.0
1 1 1
2.0.0
2 2
3.0.0
3 3
End2EndT
18. 19
Config ChatOps IT Autom
Deploy Test Observe
Mastering Continuous Delivery: $ keptn new artifact myservice:4.0.0
S
T
A
G
I
N
G
P
R
O
D
ScoreDirect PerformanceUpdate Promote?C D T O
ScoreBlue/GreenUpdate Keep?C D O
1.0.0
1 1
1.0.0
1 1 1
2.0.0
2 2
3.0.0
3 3
4 4 4
End2EndT
4.0.0
4.0.0
4 4 95
/
100
90
/
100
K
E
E
P
P
R
O
M
O
T
E
19. 20
4 4
Config ChatOps IT Autom
Deploy Test Observe
Self-Healing Production: $ keptn new problem <Services, Root Cause>
P
R
O
D
Evaluate
Decide
Act
Notify
4 Escalate
4 4
20. 21
Advantages of the Keptn approach
• Uniquely combine delivery and operations automation
• Separation of the what (shipyard) from the how (uniform)
• Change a process or exchange a tool in minutes
• GitOps and cloud-native best practices out-of-the-box
• Easy extensibility via event-based model
• Declarative approach vs. copy & paste pipelines
21. Confidential 22
MTTI
= Mean Time to Innovation
MTTR
Mean Time to Remediate
4.8 days
4 hours
~ 10min
12.5 days 2 days ~ 1 hour
We are building keptn to re-shape this reality
GROW this number!
24. What is
Andreas Grabner, Dynatrace
@grabnerandi
@keptnProject
https://keptn.sh
https://github.com/keptn
Notes de l'éditeur
We did a survey with most of our attendees at PERFORM 2019 in Las Vegas – asking them questions around their cloud native projects. Please take the URL and do the survey as well!
I looked at two metrics that tell me how mature an organization is:
MTTI: how long does it take to get a newly built and already tested feature from pre-prod into production? 1 hour was the benchmark that our CTO gave us internally!
MTTR: how long does it take to remediate any problems that may come up? This should be in the range of minutes, not hours or days!
The shocking truth of this survey was that only 5% of our customers are reaping the benefits of new technology. The majority is in the bottom left half where they would have assumed that new technology gets them to the top right „magic quadrant“
Many teams we spoken with build their own
Deployment Pipelines: Combination of OpenSource & Commercial Tools for Deployment Automation!
Testing Pipelines: Combination of OpenSource & Commerical Tools for Test Execution
Quality Gates: Most often done manual. Some are investing in automated validation!
Auto Remediation: Mostly done manual with a trend towards simply remediation actions
Numbers based on our survey – https://dynatrace.ai/acsurvey