Menu
Progressive Delivery in the Kubernetes era
Natale is a Software Engineer and Solution Architect with more than 10 years of expertise on IT and ICT technologies and a consolidated background on telecommunications, DevOps and Linux operating systems.
Today Natale is Lead Developer Advocate at Red Hat. He is co-author of “Modernizing Enterprise Java” and “GitOps Cookbook” books for O’Reilly, helping people within communities and customers have success with their Kubernetes and cloud native strategy.
Kevin is a software engineer currently working as developer advocate at Red Hat who is on a mission to supercharge developer joy and productivity using Open Source as the guiding light. Kevin previously worked as a (Lead) Software Engineer at a variety of organizations ranging from small startups to large US enterprises and even the Belgian public sector. When not hacking away on his computer or talking at conferences, you can find Kevin somewhere in the wild hiking, gravel biking, snowboarding down mountains or packrafting (up and) down WW rivers.
Abstract
Production is the place where all applications should live. Even though you are using continuous integration and delivery, you might wonder every time you release a new version to production if it will work or there will be some breakage on the latest version, eventually making production unavailable to the customers.Â
Progressive delivery is the next step after Continuous Delivery to test your application in production before it becomes fully available to all your user bases.
Embrace progressive delivery with techniques like the blue-green, canary release, shadowing traffic, or dark launches to validate the application in production using Kubernetes and tools like Istio, Prometheus, ArgoCD, or Argo Rollouts.
Come to this session to learn progressive delivery and GitOps in action using Kubernetes.
