Expanding Interoperability in the CD ecosystem - CDCon - Austin, TX - 2022
0 likes149 views
This document discusses using event-driven integration with CDEvents to glue together different continuous delivery tools. It presents a scenario where developers need to provision environments on demand and configure them with various tools. CDEvents and Knative Eventing can be used to route events between these tools to provide visibility and avoid point-to-point integrations. The document describes a demo of provisioning and using a new environment. It also discusses challenges, such as different integration styles across Kubernetes projects and the need for CDEvents to support more than just event emission.
Expanding Interoperability in the CD ecosystem - CDCon - Austin, TX - 2022
- 2. Expanding Interoperability in the CD Ecosystem Mauricio Salatino Ishan Khare (couldn’t make it) Austin, Texas USA 2022
- 3. ● Use Case / Scenario ○ Challenges ○ Why CDEvents? ● Demo ● Next Steps Agenda
- 4. ● Mauricio Salatino @Salaboy ● Staff Engineer @VMware ● Full time on @KnativeProject OSS ● CD Foundation Ambassador ○ SIG-Events member ○ CDEvents Go SDK ● Writing a book ○ 35% Discount code: ctwcdcon22 A bit about myself
- 5. Scenario
- 6. ● We want to build a platform that: ○ Allow developers to provision Environments on demand ○ Configure those Environments with tools that our developers need ○ Provides extension points for other tools to be integrated ● We need to: ○ Glue different tools to achieve this use case ○ Avoid building point to point glue, for example integration between Tool A and Tool B that cannot be reused for Tool C What do we want to achieve?
- 7. The tools that we will be using
- 8. The tools that we will be using
- 9. The tools that we will be using
- 10. The tools that we will be using
- 11. The tools that we will be using
- 12. The tools that we will be using
- 13. The tools that we will be using
- 14. ● We want visibility across different tools and Clusters ● We want to implement an event-driven integration approach ○ We don’t want to build point to point integrations for every tool that we want to use, we want them to speak the same language ● We know that we will be adding more tools that haven’t been designed to work together ● We can use tools like Knative Eventing to route CloudEvents Why using CDEvents?
- 15. Platform Cluster
- 17. Demo Flow 1) Request an Environment 2) Use the Environment
- 18. New Environment is requested
- 19. The environment is provisioned and then ..
- 20. Tools will be installed
- 21. Using the new Environment
- 22. Demo Time
- 23. Demo Time
- 24. Plot Twist!
- 25. ● Kubernetes projects can be extended with new controllers but each project has its own style ○ Knative & Tekton Sample Controller ○ Crossplane Sample Controller ○ Keptn integration mechanisms (inbound and outbound) ● We need for SDKs in different languages, Java is coming along ● CDEvents semantics are currently focused on emitting events only ○ We have created our own “Orchestrator” events ● The vocabulary will only evolve if it is being used ○ We need more adopters joining the CDEvents WG with use cases and challenges Challenges, nasty ones
- 26. ● Knative Kubernetes APIServerSource: https://knative.dev/docs/eventing/sources/apiserversource/reference/#apiserversource Extending Kubernetes using Events
- 27. ● Knative Functions: https://knative.dev/knative-sandbox/kn-plugin-func Extending Kubernetes using Events
- 28. Thanks! ● Follow me on Twitter: @Salaboy ● Get in touch if you want to contribute ● Continuous Delivery for Kubernetes ○ www.manning.com ○ 35% Discount code: ctwcdcon22