The goals of this talk is to explain the different between two common continuous deployment strategies for Kubernetes clusters.
There are two common strategies to continuous deployment to Kubernetes-based environments. The first one is a push based model, where a deployment pipeline (e.g. Jenkins / Azure Devops /…) pushes new applications to a container cluster. A second approach is a pull based model (e.g. Flux / Argo ) where services running on the cluster will pull new application configuration into the cluster.
In this talk we'll discuss both approaches, and do a compare and contrast between them. We'll also see a demo of both approaches to continuous delivery on a Kubernetes Cluster.
DeveloperWeek Global: Enterprise 2020
Get your ticket or
log in to build your agenda.
Approaches to Continuously Delivering Applications on Kubernetes
Nills has been working with cloud technologies for the past 7 years. In his current position as a cloud solution architect he helps key Microsoft customers adopt Azure. His main focus areas within Azure are automation, networking and Kubernetes.
In his spare time Nills enjoys running and enjoying one of many Belgian specialty beers.
Download these images to your phone and post using the Instagram app.