Guzman

Hi, When I reached [step 6 of the sample app tutorial](https://knative.dev/docs/bookstore/page-6/advanced-event-filtering/#step-1-create-the-trigger-for-database-insertion) I noticed that the event never reached the subscriber (node-server service). If I understand correctly, this is because when...

This doesn't seem to be bothering others, and it is not a trivial change after all. Should we leave it as-is? @dprotaso @Leo6Leo

Thanks for your input @Leo6Leo. After checking this again, I doubt adding a `port` field to `KReference` is the way forward here: `KReference` is a generic structure to refer to...

> I think circling back here - I think we should drop the port-forward instructions and just recommend people use the Kind LoadBalancer - https://kind.sigs.k8s.io/docs/user/loadbalancer > > If they're using...

@dprotaso that looks much better! Closing this, thanks!

This change is part of the following stack: - #17255 - #17243 - #17320 - #17328 - #17375 ◀ - #17526 Change managed by [git-spice](https://abhinav.github.io/git-spice/).

This change is part of the following stack: - #17255 - #17243 - #17320 - #17328 - #17595 - #17526 ◀ Change managed by [git-spice](https://abhinav.github.io/git-spice/).

/retest

> > Internal errors indicate server-side bugs or corrupted state that are unlikely to resolve on retry. Retrying these errors can mask underlying issues and delay proper error handling. >...

> We somewhat frequently change something in the retry logic due to flakes. So I believe some refactoring to make this easier and more consistent is worth it. What if...