johnthompson-ybor
johnthompson-ybor
having to use istioctl to do stuff is a non-starter for many people. We absolutely need a declarative way to do this.
This fixes: https://github.com/akuity/kargo/issues/4793
I wanted to match the argocd spec On Mon, Sep 1, 2025 at 8:32 AM Hidde Beydals ***@***.***> wrote: > ***@***.**** commented on this pull request. > ------------------------------ > >...
That's for events you're subscribed to -- i'm talking about publishing events -- see this from client go: https://github.com/kubernetes/kubernetes/blob/9568a2ac145cf9be930e3da835f86c1e61f7f7c1/staging/src/k8s.io/client-go/tools/record/events_cache.go https://dev.to/shuheiktgw/kubernetes-event-aggregation-and-spam-filtering-in-client-go-25mn A perhaps more informative blog post.
It's quite possible I'm misunderstanding how this works, but the main issue is if i'm publishing the _exact same event_ multiple times with the kube-rs recorder, it doesn't get aggregated...
I thought the same thing, but I just confirmed and that's what version I'm on.
What's the status on this fix, just ran into this problem again :(
i saw this myself and noticed that it only comes up if i restart the kserve pods (version 0.15)