mitzen

In this blog, we will be setting envoyfilter that uses lua to intercept and log payload,  Ground work We will be using httpbin that is shipped as part of istio samples for our sidecar setup.  kubectl apply -f gateway.yaml kubectl apply -f httpbin.yaml And then we can create our envoyfilter. This is what our envoyfilter looks like this. Points to note : we are enabling buffering. Without buffering, the lua won't log and there won't be any output in the istio-proxy container log.  Before apply the script below ensure you have set the logging level - otherwise you might not see the logs details. You need to configure the logging level with the following command:- istioctl proxy-config log httpbin-65bbd9c89d-n449w --level lua:info Next we will apply the following script apiVersion : networking.istio.io/v1alpha3 kind : EnvoyFilter metadata :   name : log-payload   namespace : default spec :   workloadSelector :     labels :       app : h...

Top 10 Continuous Delivery Anti-Patterns (2025) 1 “Pipeline Theater” Automated steps that  look  like CD but don’t enable safe, fast releases. — e.g., “We have a pipeline!” but: • Manual gate between every stage • Tests take 4+ hours • No rollback capability Creates false confidence . Teams think they’re doing CD while still blocked, slow, and high-risk. CD is about outcomes (lead time, reliability), not tooling. 2 Monorepo + Microservices = Mega-Pipeline One giant pipeline for 50+ services — changes to  service-a  trigger full rebuild of all. Wastes resources, causes queueing, discourages commits → kills trunk-based flow . Optimize for small batches & fast feedback. 3 GitOps ≠ CD Using Argo CD/Flux to sync  manifests  — but builds, tests, and approvals still happen outside the pipeline. e.g., “We GitOps!” but: • JAR built on dev laptop • No automated quality gates • Image tag = latest Confuses deployment sync with delivery . You’re doing continuous de...