Kubernetes has evolved to provide capabilities for managing the lifecycle of distributed applications such as deployment, scaling, configuration, and isolation of resources. It addresses needs such as service discovery, networking, bindings to APIs, and state management through controllers, custom resources, and extensions like operators, service meshes, and serverless platforms like Knative. Emerging technologies are exploring hybrid deployments, edge computing, improved state abstractions, and integration across runtimes and clouds.

1. Kubernetes:
The evolution of distributed systems

2. @bibryam
Bilgin Ibryam
● Product Manager at Red Hat
● Former Architect/Consultant
● Committer at Apache Camel
● Author and blogger
○ Camel Design Patterns
○ Kubernetes Patterns
@bibryam

4. @bibryam
Distributed application needs

5. @bibryam
Distributed application needs
Lifecycle management
● Deployment/rollback
● Placement/scheduling
● Configuration management
● Resource/failure isolation
● Auto/manual scaling
● Hybrid workloads
○ stateless, stateful, tasks, serverless

6. @bibryam
Distributed application needs
Advanced networking
● Service discovery and failover
● Dynamic traffic routing
● Resilience
○ Retry, timeout, circuit breaking
● Security, encryption, rate limiting
● Observability and tracing

7. @bibryam
Distributed application needs
Resource bindings
● Connectors for APIs
● Polling and event-driven integrations
● Point-to-point, pub/sub interactions
● Protocol conversion
● Message transformation
● Filtering, light message routing

8. @bibryam
Distributed application needs
Stateful abstractions
● Workflow management
○ Long-running transactions (SAGA)
● Temporal scheduling i.e. timers
● Distributed caching
● Idempotency
● Application storage abstraction

10. @bibryam
Health probes
Foundational primitives
Configuration management Declarative deployment
Resource demands & placement

11. @bibryam
Batch/Periodic Job
Hybrid workloads
Global SingletonStateful Service
Stateless Service

12. @bibryam
Kubernetes capabilities
● Deployment/rollback
● Automated placement
● Configuration management
● Resource isolation, recovery
● Auto/manual scaling
● Hybrid workloads: stateless, stateful,
batch jobs, serverless

14. @bibryam
Out-of-process architecture
Deployment guarantees Lifecycle guarantees

15. @bibryam
Sidecar

16. @bibryam
Controller Pattern
Schemas
● ReplicaSet
● StatefulSet
Controllers
● replicaset
● statefulset
Resources
● Pod
● PVC...
CustomResourceDefinition + Custom controller = Operator

17. @bibryam
How to extend Kubernetes?
Sidecar Operator
Out-of-process composition
mechanism for orthogonal
capabilities.
Define domain-specific knowledge in
executable Kubernetes
primitives.
Data plane Control plane

19. @bibryam
What is Service Mesh?

20. @bibryam
What is Service Mesh?

21. @bibryam
What is Service Mesh?

22. @bibryam
What is Service Mesh?

23. @bibryam
Service Mesh & API Gateway capabilities
Advanced networking
● Service discovery and failover
● Dynamic traffic routing
● Retry, timeout, circuit breaking
● Security, rate limiting, encryption
● Observability and tracing

24. @bibryam
What is Knative?
Serving
Common infrastructure
for request-driven
interactions that can
"scale to zero".
Eventing
Common infrastructure
for consuming and
producing events
declaratively.
Kubernetes-based platform to deploy, and manage
serverless workloads.

25. @bibryam
Knative Serving
● Scale-to-zero & activation
● Rapid autoscaling
● Traffic splitting
● Callable by Knative eventing
● Simplified deployment model
apiVersion: serving.knative.dev/v1alpha1
kind: Service
metadata:
name: lotto
spec:
replicas: 1
selector:
matchLabels:
app: lotto
template:
metadata:
labels:
app: lotto
spec:
containers:
- image: cds19/lotto

26. @bibryam
Knative Eventing

27. @bibryam
Knative Eventing
● Source Importers
(Kafka, Apache Camel 200+)
● Broker implementations
(In-memory, Kafka, etc)
● CloudEvents as the data format
● Triggers and filters

28. @bibryam
Knative capabilities
● Serving
○ Autoscaling, scale-to-zero
○ Traffic splitting
● Eventing
○ Messaging infrastructure
○ Source importers

29. @bibryam
What is Dapr?
A portable runtime for building distributed
applications.

30. @bibryam
Building blocks

31. @bibryam
Dapr architecture

32. @bibryam
Dapr on Kubernetes

33. @bibryam
Dapr capabilities
● Stateful primitives
● Resource bindings
● Advanced networking

34. @bibryam
The list goes on...
Hybrid cloud, and edge-to-edge application networking
Stateful abstractions for serverless applications
Camel K - Kubernetes native integration framework
Log collection, OpenID authentication, caching...

36. @bibryam
New developments
Lifecycle
● Better sidecars kubernetes/753
● More operators, better operators
operatorhub.io
Networking
● Data Plane Development Kit (DPDK)
● Envoy: More L7 protocols, Wasm
Bindings
● Bindings move out of the application
● More resource bindings for Dapr, Knative
State
● More work is needed!
● No pluggable, polyglot stateful
abstractions for federation, CDC,
caching, idempotency, etc.

37. @bibryam
Multi-runtime services ecosystem

38. @bibryam
Business logic and distributed primitives

39. @bibryam
What comes after Microservices?

40. @bibryam
https://k8spatterns.io