K8S CD is simple in theory. But in practice — how do we manage K8S changes? GitOps, Progressive Delivery, Service Meshes, Canary… Most of us have it in the roadmap "for the next year". But what will we use when that year arrives? ArgoCD, Flux, Keptn, Tekton, JenkinsX, Shipper? Many options, not enough clarity.

And then – there are the gaps none of these tools can currently close. Do we wire things up ourselves again?

Let’s figure out how, why, and what are the options.