Ilya Dmitrichenko

> torn on this; go would be much simpler and erb would be more familiar to devops-y types I know what you mean... there is [Ego](https://github.com/benbjohnson/ego), but it's a kind...

We have found this behaviour quite surprising when trying to use a compose file with about a dozen services for [our microservices reference app](https://github.com/microservices-demo/microservices-demo/blob/master/deploy/docker-compose/docker-compose.yml). cc @bchav

I've looked at the code, and it seems like this a very fundamental assumption and it'd would require significant amount of work to fix, and unfortunately the code is not...

> I'd wish I could figure out a simple fix. I mean, a fix in Go code that I could submit as a PR, not a work-around (we have already...

Quick high-level question before I look at the code, was this an optional behaviour already, or was pod deletion done unconditionally?

> We should direct efforts towards troubleshooting and improving this in Hubble, without creating technical debt here. I fully agree with Timo on this. Perhaps one way to go about...

@ti-mo oh! I was assuming flows were being streamed...

Might be a good reason to implement https://github.com/cilium/cilium-cli/issues/115.

There is also [a library](https://github.com/kubernetes-sigs/kubebuilder-declarative-pattern/blob/51b541d068b8/pkg/patterns/declarative/pkg/applier/direct.go) that implements server-side-apply functionality with a fallback to client-side implementation that uses same code as `kubectl apply` does.

I'm seeing this on GKE also: https://github.com/cilium/cilium/runs/3557961582?check_suite_focus=true#step:14:29