Stefan Prodan

@michaelbeaumont have you tested the kubeconfig flag? Based on this reporting seems broken https://github.com/fluxcd/flagger/issues/694

Because we add owner refs to the generated objects, and the owner object (the canary) is not present on that cluster, only the TrafficRoutes are.

@michaelbeaumont ah good point, thanks for the explanation.

I would add the source after NAME

Maybe we should leave this as it is and improve `flux get` where we can do aggregations.

Flagger does support VirtualService delegation, maybe that solves your issue?

This is by design, changing the bootstrap target or auth method is not supported. You need to do `flux uninstall` or delete the `flux-system` secret with kubectl.

@phillebaba @SomtochiAma does it make sense to add templating to CommitStatus if the actual message is limited to a couple of characters ? Maybe adding `prefix` is enough to solve...

@SomtochiAma we need to take into account things like https://github.com/fluxcd/notification-controller/pull/369 it's not a commit status but it's not an alert either...

> My opinion is that this should only cover CommitStatus as it seems to be a well defined term within most Git providers today. Agreed, I've merged the GitHub dispatch...