Kubernetes helps us tame sprawling microservices architectures and addressing the increased operational complexity. Kubernetes gives developers abstractions and APIs to deploy and run their services.
Yet, the elephant in the room is that to run, maintain and evolve the Kubernetes clusters, we need more ops expertise and most likely a dedicated team to do so.
The question that begs to be asked is if we are going back to pre-DevOps isolation between Dev and Ops teams? Is the tradeoff between better operational tools and introducing a new dependency layer on the path for application teams to deliver and run their services worthwhile? Are we making life easier for application teams or instead reducing their end-to-end ownership?
Team Topologies is a structured approach for thinking about teams responsibilities and interactions which can help us get the most value out of Kubernetes adoption.
This talk draws on research and case studies from the Team Topologies book by Matthew Skelton and Manuel Pais (IT Revolution Press, 2019) together with first-hand consulting experience from the authors with organizations around the world.
Strategies for Landing an Oracle DBA Job as a Fresher
The Elephant in the Kubernetes Room: Team Interactions at Scale @ DevOpsDaysMadrid, Feb 2020 (keynote)
1. TeamTopologies.com
@TeamTopologies
The Elephant in the
Kubernetes Room
Team Interactions at Scale
Manuel Pais, Consultant
co-author of Team Topologies - @manupaisable
DevOpsDays Madrid 2020
#devopsdays
2. 2
Is Kubernetes a Platform?
Dev and Ops Equilibrium
Team Cognitive Load
Team Interactions
3. Team Topologies
4
Organizing business and
technology teams for fast flow
Matthew Skelton & Manuel Pais
IT Revolution Press (2019)
https://teamtopologies.com
10. 11
Still need to...
… sizing hosts
… create/destroy clusters
… update to new K8s versions
… decide on namespaces vs clusters
<insert your fav chore here>
11. 12
Still need to...
… sizing hosts
… create/destroy clusters
… update to new K8s versions
… decide on namespaces vs clusters
worry about security
15. “A digital platform is a foundation of
self-service APIs, tools, services,
knowledge and support which are
arranged as a compelling internal
product.”
– Evan Bottcher, 2018
16
44. Team Topologies
49
Organizing business and
technology teams for fast flow
Matthew Skelton & Manuel Pais
IT Revolution Press (2019)
https://teamtopologies.com
49. 56
Low-level AWS service calls (EC2, IAM, STS, Autoscaling, etc.) from January 2015 to January 2017
50. “We didn’t change our organization
because we wanted to use
Kubernetes, we used Kubernetes
because we wanted to change
our organization.”
- Paul Ingles
57
53. 61
… in order to reduce
extraneous cognitive load
on stream-aligned teams
Platform Purpose
54. “We wanted to scale our teams but
maintain the principles of what
helped us move fast: autonomy,
work with minimal coordination,
self-service infrastructure.”
- Paul Ingles
63
61. “Kubernetes helps us in a few ways:
- Application-focused abstractions
- Operate and configure clusters to
minimise coordination ”
- Paul Ingles
70
66. 75
2018
Infra platform
started with few
services
First customer
(centralized
logging, metrics,
auto scaling)
2019
Started using SLAs
and SLOs, clarifying
reliability/latency/etc
Growing traffic in
platform vs AWS
67. 76
...
Addressed critical
cross-functional
needs (GDPR,
security, alerts +
SLOs as a service)
Adoption by HRMT
(Highest Revenue
Making team)
2018
Infra platform
started with few
services
First customer
(centralized
logging, metrics,
auto scaling)
2019
Started using SLAs
and SLOs, clarifying
reliability/latency/etc
Growing traffic in
platform vs AWS
68. 77
...
Addressed critical
cross-functional
needs (GDPR,
security, alerts +
SLOs as a service)
Adoption by HRMT
(Highest Revenue
Making team)
2018
Infra platform
started with few
services
First customer
(centralized
logging, metrics,
auto scaling)
2019
Started using SLAs
and SLOs, clarifying
reliability/latency/etc
Growing traffic in
platform vs AWS
88. How well can the team understand the
platform/Kubernetes abstractions they
need to use on a regular basis?
1 - Assess cognitive load
116
89. What’s the gap between your
Kubernetes implementation and an
internal digital platform?
2 - Define your platform
117
90. Who is responsible for what? Who is
impacted? How do you collaborate on
new platform internal services?
Collaboration vs X-as-a-Service
3 - Team Interactions
118
91. Zalando Kubernetes at Zalando
Mercedes DevOps Adoption at Mercedes-Benz.io
Twilio Platforms at Twilio: Unlocking Developer Effectiveness
Adidas Where Cloud Native Meets the Sporting Goods Industry
ITV ITV's Common Platform v2 Better, Faster, Cheaper, Happier
MAN Truck & Bus How to Manage Cloud Infrastructure at MAN Truck & Bus
Farfetch UX I DevOps - The Trojan Horse for Implementing a DevOps Culture
More platform examples
119