Mandar U Jog

Applying rate limit from “ingress” is already supported by adding a config override with Destination: productpage Source: istio-ingress Applying per service rate limit “at” ingress is not support yet.

That field was added as part of securing Istio components work about two weeks ago and it is available in master. https://github.com/istio/api/commit/d80e4d55d86452dbb5de8ee24b37bf5c5124a9bc Are you trying to use this file with...

Yes, this means `istioctl` is older from before this change was made. Please use a more recent `istioctl`

TUN makes it easy to integrate with local policy routing, we can similarly use it to create TUNs in separate network namespaces for hermetic testing.

@fpesce we do not have ci/cd setup here yet. We will need to park the PR here until ci/cd is setup. Also dco did not work :-)

@bianpengyuan can you setup basic ci/cd ?

@douglas-reid related to https://github.com/istio/istio/issues/11475

@gargnupur is adding a full working example to docs using existing envoy filter. Istio 1.7 will have extension api that will provide a supported way to configure native rate limiting.

@ostromart you changed the defaults recently to have replica counts =2, right? is this resolved by that fix?