Kubernetes, Istio e Knative: The new cloud stack

Over the years architectural styles have evolved with microservice, service mesh and serverless. Would not it be nice to have all of them working together to add value to our business?

Well, I introduce the new cloud stack: Kubernetes, Istio and Knative that are totally open source.

So, in this talk I will introduce the newest member of the team, the Knative! Which brings the serverless feature in our architecture, using Istio to route traffic between versioned functions, among other characteristics that I will demonstrate during the course of the lecture.

Transcript

1. Kubernetes, Istio e Knative: The new cloud stack Luram Archanjo
2. Who am I? • Software Engineer at Sensedia • MBA in Java projects • Java and Microservice enthusiastic
3. Agenda • Serverless • Knative & Components • Why Kubernetes & Istio? • Demo • Questions
4. What is Serverless?
5. What is Serverless? Serverless computing, is an execution model where the cloud provider is responsible for executing a piece of code by dynamically allocating the resources. Source: https://serverless-stack.com & https://martinfowler.com/articles/serverless.html Scalability Reduced operational cost Time to market
6. What is Knative?
7. What is Knative? Kubernetes based open source building blocks for serverless Source: https://knative.dev
8. Knative Components
9. Knative Components Source: https://knative.dev
10. Knative Components Serving How your code receives requests and scales with them: • Automatic scaling up and down to zero • Multiple revisions of same function • Route traffic across revisions Eventing How your code is triggered by events: • Functions consume and publish events • Multiple event sources available • Encourages asynchronous Build How your code is built and packaged as a container: • Pluggable model to build • Build in-cloud or on-cluster • Templates available
11. How Build works?
12. How Build works? Source: https://knative.dev Code Container Image Registry
13. How Serving works?
14. How Serving works? Source: https://knative.dev Service Manages the whole lifecycle of your workload. Configuration Maintains the current/desired state for your deployment. Revision A point-in-time snapshot of code and configuration. Route Maps and manage traffics to revisions.
15. How Serving works?
16. How Serving works?
17. How Serving works?
18. How Serving works?
19. How Eventing works?
20. How Eventing works? Source: https://knative.dev
21. How Eventing works? Source: https://knative.dev
22. Why Kubernetes?
23. Kubernetes • Horizontal scaling • Auto-scaling • Service discovery and Load balancing • Self-healing
24. Why Istio?
25. Istio • Traffic management ◦ Traffic Routing • Security ◦ East-West ◦ North-South • Observability ◦ Metrics ◦ Traces ◦ Logs
26. Demo
27. Summary 2º Place 1º Place 3º Place Build on top of Kubernetes and Istio • Automatic scaling up and down to zero • Route traffic across revisions • Load-balancing Flexibility and No Vendor Lock-in • Cloud • Premises • Third-party data center Serverless Experience in a Containerized Environment • Immutability • High Scalability • Pipeline Management
28. Thanks a million! Questions? /larchanjo /luram-archanjo