John Howard
John Howard
> @douglas-reid @howardjohn refactor base on #39751, please review again. > > do we need backport this to v1.13/v.14, cause there's a warn validating. > > https://github.com/istio/istio/blob/d9762744d63553d6929a2b548ae8300cd3d78eb4/pkg/config/validation/validation.go#L3665 I don't think...
I think the `envoy.dynamic.ot` is probably an Envoy internal thing. Can you get full logs (debug not needed) and config dump from one of the impacted proxies?
From the config perspective, all config looks right. Which I am wondering if that means it cannot reach your tracing service (jaeger-collector.istio-system)
Does it occur on newer versions? I recall fixing similar
Istio 1.11 is end of life.
Both (2) taint controller and my proposed new change would
One other thing is this would allow adding a node selector to the CNI daemonset to deploy it on a subset of nodes. Then the injected pod selector ensures we...
Hm, with my node selector thing Cluster autoscaler seems to work on GKE.
Discussed in the WG meeting (beforethe autoscaler issue). If we can make sure autoscaling works then I think the plan is: * In 1.16, add new node selector and logic...
Anything I can do to get more info here?