Michal Hruby

That's signature of a zip64 file, this library doesn't support those. You should try [yauzl](https://github.com/thejoshwolfe/yauzl) or [unzip-stream](https://github.com/mhr3/unzip-stream).

I've just published [unzip-stream](https://github.com/mhr3/node-unzip) which focuses specifically on streaming unzipping.

I've just published a fork of unzip - [unzip-stream](https://github.com/mhr3/node-unzip) which bumps the dep (and fixes bunch of other stuff).

If you're still having this issue, I've published [unzip-stream](https://github.com/mhr3/node-unzip) which should solve it.

Longer version of the logs ```ini level=debug ts=2024-01-06T23:37:08.042589986Z caller=operator.go:695 component=alertmanageroperator key=monitoring/prometheus-stack-kube-prom-alertmanager msg="new statefulset generation inputs match current, skipping any actions" level=info ts=2024-01-06T23:37:08.042630588Z caller=operator.go:641 component=alertmanageroperator key=monitoring/prometheus-stack-kube-prom-alertmanager msg="sync alertmanager" level=debug ts=2024-01-06T23:37:08.04266028Z caller=operator.go:1048...

Here's the profile  [operator.prof.zip](https://github.com/prometheus-operator/prometheus-operator/files/13853016/operator.prof.zip) As for the cluster, it's fairly small, about 25 nodes, mostly default config from kube-prom-stack, with about a dozen extra servicemonitors. Fwiw we have a...

Metrics:  To make it easier to read, top chart, there's 3 non-zero series all overlaid on top of each other: `{controller="alertmanager", triggered_by="Secret"}` `{controller="prometheus", triggered_by="Secret"}` `{controller="prometheus-agent", triggered_by="Secret"}`

According to the logs, these are the only secrets that get updated: ``` alertmanager-prometheus-stack-kube-prom-alertmanager alertmanager-prometheus-stack-kube-prom-alertmanager-generated alertmanager-prometheus-stack-kube-prom-alertmanager-tls-assets-0 alertmanager-prometheus-stack-kube-prom-alertmanager-web-config prometheus-prometheus-stack-kube-prom-prometheus prometheus-prometheus-stack-kube-prom-prometheus-tls-assets-0 prometheus-prometheus-stack-kube-prom-prometheus-web-config prometheus-stack-kube-prom-admission prometheus-stack-kube-prom-prometheus-scrape-confg ``` All of them are internal to kube-prom-stack...

Anything we can do here? We see the operator use around 1.5 cpu cores 24/7.

> Hey, ping @mhr3 , would you still be willing to merge this? Just ran into the same thing and thankful you already have the fix. I don't have privileges...