Closed ldemailly closed 7 years ago
I don't think this is a good idea. We have covered 90% of Envoy config. Allowing people to break istio while trying to provide seamless experience is contradictory.
Very few people have asked for this.
it should be possible to patch or change config without making a new release - if only for emergency fixes
Plausible but difficult to reconcile custom templates with machine-generated config. Feels like a hacky workaround overall. Assigning it to you to think of ways to reconcile the two.
putting it for 0.3 as I'm pretty sure we'll learn in 0.2 and rawvm that we need this
Issue moved to istio/istio #1396 via ZenHub
there should be an optional "merge" or "patch" or externalized template so people can tweak the resulting envoy configs
ps: it does mean they can also break istio but that's not a reason to have it completely locked down and hardcoded like now