fixit-xdu

Should the "preferred" affinity / podnode placement configuration be consumed by more than 1 entity (`kube-scheduler`)? "required" affinity is a strong constraint without room for inconsistency but this doesn't apply...

sorry to bother you @howardjohn would you mind sharing your thoughts on this? due to my limited knowledge of istio/envoy proxy, I've been stuck on this issue for a week...

@howardjohn not sure how you intend to dump trace logs but I set `global.proxy.logLevel: trace` to get trace logs. The volume of the log is very overwhelming for a human...

@ramaraochavali thx for the response! > All of the envoy initialization happens on the main thread is there any reason why this has to be synchronous? processing records seems pretty...

@ramaraochavali @howardjohn is there a way configure `istio` to disable envoy's [active health check](tcp_health_check) for upstream clusters?

dumb question for @howardjohn: when I run `istioctl proxy-config endpoints . -n `, the results shows a column for healthiness status: ``` ENDPOINT STATUS OUTLIER CHECK CLUSTER 10.230.101.112:5000 HEALTHY OK...

> it's just explicitly passed as healthy in the xds would you mind pointing me to the source code?

from [here](https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/operations/init#initialization): > Envoy is always guaranteed to initialize within [initial_fetch_timeout](https://www.envoyproxy.io/docs/envoy/latest/api-v3/config/core/v3/config_source.proto#envoy-v3-api-field-config-core-v3-configsource-initial-fetch-timeout), with a best effort made to obtain the complete set of xDS configuration within that subject to the management...

thank you @ramaraochavali prior to adding the `ServiceEntry`s the initial load time was fine with the same amount of k8s `Service` objects. (context: I recently added a few hundred `ServiceEntry`...

@ramaraochavali I've compared the `config_dump` from `istio-proxy` and please correct me if I misunderstood the scope: I don't see a global setting in bootstrap config and I should add `wait_for_warm_on_init:...