Sandro
Sandro
@gnarl not only then i would have to add. But it always happend while doing an update because every pod gets recreated
Wouldnt it be possible to "just" publish them to a secondary Location like quay.io or something owned from netapp. This is stupid rate limiter has already killed my trident updates...
Hi @gnarl , have you checked on RHEL CoreOS Nodes ? I just checked one of my Clusters again and can see the error again. `Could not run lsscsi: exit...
No to my Information its a pretty basic OCP Cluster with no Modification that should effect something like this
Hey i can als help :)
Hi, i also would heavily vote for dedicated variables per Image :) Currently i could specify `tridentImage` which is already good but sadly im not able to pull the OperatorImage...
Hi @ntap-arorar , Thanks for that I'll try that tomorrow :) Do you see any chance of publishing the image also on quay.io That would already fix 90% of my...
Im running `enterprise-logs:3.5.1` and the issue is still present: ``` enterprise-logs-write-5 loki level=error ts=2025-06-04T10:47:18.90917322Z caller=push.go:202 org_id=foo msg="negative structured metadata bytes received" userID=foo retentionHours=2160 isAggregatedMetric=false policyName= size=0 ```