O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.

CNCF Webinar: Building a Cloud Native Technology Stack that Supports Full Cycle Development

Kubernetes can unlock rapid development cycles and increased feature velocity. Kubernetes also disrupts your software development lifecycle. Organizations that have successfully embraced cloud-native technologies like Kubernetes have invested heavily in creating a self-service application platform to enable Full Cycle Development.
How can you make sure your developers are empowered and your organization is getting all the benefits a technology like Kubernetes has to offer?
In this webinar, we will discuss the four capabilities that are essential to Full Cycle Development: container management, progressive delivery, edge management, and observability:

– Container Management with Kubernetes. Manage and run container-based applications at scale and on a variety of infrastructures.
– Progressive Delivery with Continuous Delivery Pipelines. Support the creation of pipelines that enable the automated build, verification, deployment, release, and observability of applications by developers.
– Edge Management with a Self-Service API Gateway. Enable developers to release new functionality in a self-service manner.
– Observability with an Observability Stack. Allow developers and platform teams to collect and analyze end-user and application feedback.

Join this webinar will talk through the requirements for these technologies as well as discuss common antipatterns and how to avoid them

Recording: https://www.cncf.io/webinars/building-a-cloud-native-technology-stack-that-supports-full-cycle-development/

  • Seja o primeiro a comentar

CNCF Webinar: Building a Cloud Native Technology Stack that Supports Full Cycle Development

  1. 1. Building a Cloud-Native Technology Stack that Supports Full Cycle Development Daniel Bryant Product Architect, Ambassador Labs (formerly Datawire)
  2. 2. @danielbryantuk ● Being fully cloud native requires new tech and new workflows ● Creating a supporting cloud platform is essential: ○ Container orchestration ○ Progressive delivery ○ Edge management ○ Observability ● Consciously design your platform & watch for antipatterns tl;dr
  3. 3. @danielbryantuk @danielbryantuk
  4. 4. @danielbryantuk A quick cloud native primer... ● Going “cloud native” offers benefits, but requires changes: ○ New technologies ○ Appropriate culture ○ New workflows ● Successful cloud native organisations have: ○ Created a self-service application platform ○ Adopted new tools and (full cycle) developer workflows
  5. 5. @danielbryantuk https://netflixtechblog.com/full-cycle-developers-at-netflix-a08c31f83249 Full Cycle Developers
  6. 6. @danielbryantuk Full Cycle Developers: Team Topologies
  7. 7. @danielbryantuk 1. Container management 1. Progressive delivery 1. Edge management 1. Observability Four cloud native platform requirements
  8. 8. @danielbryantuk More Details on Full Cycle and K8s https://blog.getambassador.io/enabling-full-cycle-development-are- you-benefiting-from-your-move-to-kubernetes-d9eab2e94e7 ● Successful cloud native organisations have: ○ Created a self-service application platform ○ Adopted new tools and (full cycle) developer workflows
  9. 9. Avoiding Platform Antipatterns
  10. 10. @danielbryantuk Avoiding Platform Antipatterns Centralized Control and Ownership: One Size Doesn’t Fit All Fragmented Platform Implementation Slow Development Loops: Less Time Coding, More Time Toiling
  11. 11. @danielbryantuk Antipattern: Centralized Control and Ownership ● (Dis)economies of scale ● Overzealous guardrails ● Modification is ticket-driven
  12. 12. Antipattern: Fragmented Platform Implementation https://speakerdeck.com/stilkov/microservices-patterns-and-antipatterns-1?slide=12
  13. 13. Antipattern: Slow Development Loops https://mitchdenny.com/the-inner-loop/
  14. 14. Exploring the Platform Capabilities
  15. 15. @danielbryantuk 1. Container management 1. Progressive delivery 1. Edge management 1. Observability Four Core Platform Capabilities
  16. 16. Container Management: Kubernetes
  17. 17. @danielbryantuk Manage and run container-based applications at scale and on a variety of infrastructures ● Developers ○ Self-service interactions: automated and observable ● Platform team ○ Set policies around access, control, and auditability Container Management
  18. 18. @danielbryantuk Kubernetes Decisions ● To self-host, or not to self-host? ● Which distro? ● Going all-in on a cloud?
  19. 19. @danielbryantuk Kubernetes Challenges ● Foundations for a PaaS-like experience? ○ Helm and Helmfile for deployment ● Developer productivity ○ Local-to-remote dev and test
  20. 20. Progressive Delivery: Delivery Pipelines
  21. 21. @danielbryantuk Supporting the creation of pipelines that enable the automated build, verification, deployment, release, and observability ● Developers ○ Self-service interactions: automated and observable ● Platform team ○ Centralize verification of quality and security properties https://redmonk.com/jgovernor/2018/08/06/towards-progressive-delivery/ Progressive Delivery
  22. 22. @danielbryantuk Progressive Delivery Decisions ● Deliver any and all application changes into production as rapidly and as safely as the organisation requires ○ Pipeline practices ○ Pipeline technology https://www.infoq.com/news/2020/03/reimagining-cicd-pipelines/
  23. 23. @danielbryantuk Progressive Delivery Challenges ● Collaboration between dev, QA, and ops ● Balance one-size-fits-all vs chaos ● Make it easy to do the right thing
  24. 24. Edge Management: Ingress and API Gateways
  25. 25. @danielbryantuk Enable the self-service release of new functionality by developers, while maintaining stability ● Developers ○ Decentralized traffic management ○ Support NFRs e.g. authn/z, retries, and circuit breaking ● Platform ○ Centralized configuration of sane defaults ○ TLS, authn/z, and rate limiting for DDoS protection Edge Management
  26. 26. @danielbryantuk Edge Stack Decisions ● Edge technologies ○ Envoy becoming the de facto standard(?) ○ xDS APIs / Ingress v2 ● Deploy/release workflows ○ Declarative (CRDs) ○ Self-service
  27. 27. @danielbryantuk Edge Stack Challenges ● Scaling edge management ● Supporting multiple protocols and NFRs https://www.getambassador.io/resources/challenges-api-gateway-kubernetes/
  28. 28. Observability: Metrics, Logging, Tracing
  29. 29. @danielbryantuk Support the collection and analysis of end user and application feedback directly by developers and the platform team. ● Developers ○ Enable product teams to observe and iterate against business goals and KPIs ● Platform ○ Observe and managing infrastructure, and ensure their service level objectives (SLOs) are met Observability
  30. 30. @danielbryantuk Observability Decisions ● Adoption (monitor all-the-things?) ● Technology selection (standards) ○ Metrics ○ Logging ○ Distributed tracing ● Joining the dots
  31. 31. @danielbryantuk Observability Challenges ● Self-service config and dashboards ● Increasing signal-to-noise ● Fault location https://medium.com/@copyconstruct/monitoring-and-observability-8417d1952e1c
  32. 32. Wrapping Up
  33. 33. @danielbryantuk ● Being fully cloud native requires new tech and new workflows ○ Lots to be learned from full cycle development ● Creating a supporting cloud platform is essential ○ Container orchestration ○ Progressive delivery ○ Edge management ○ Observability ● Consciously design your platform & watch for antipatterns In Summary
  34. 34. @danielbryantuk app.getambassador.io/ thenewstack.io/learning-kubernetes-the-need-for-a-realistic-playground/
  35. 35. @danielbryantuk Read “Building a Kubernetes Platform”: https://www.getambassador.io/learn/building-kubernetes-platform/ Subscribe to podcasts: https://www.getambassador.io/podcasts/ Follow us on Twitter: https://twitter.com/getambassadorio Ambassador CNCF Incubations proposal: https://github.com/cncf/toc/pull/435 Learning More...

×