Braunson

Any chance we can keep alive this? It's a common use case even if it will be challenging.

I think the rationale for this was an attempt to follow the W3C specification as described here: https://www.w3.org/TR/trace-context/#a-traceparent-is-received However gorouter should be following this part of the spec: https://www.w3.org/TR/trace-context/#alternative-processing Since...

I disagree @ebroberson. The line _MAY_ is contextually for cases where the proxy is also reporting its own processing, it is then optional for that component to modify the `traceparent`....

> keep from potentially breaking projects that may be relying on this functionality Again I challenge this @ebroberson.. What user is relying on the fact that gorouter is breaking the...

Would definitely be interested in trying it when it's released @mkocher Do you have a roadmap? In order to use it on our side we would want a way to...

Unless I'm missing something this seems to be an issue with your architecture or configuration. I don't see any specific reproduction instructions. If you provide a reproduction repo we might...

I found the problem. When HA is set to 3, the operator creates a PDB where `minAvailable` is set to `80%`. This will never allow any of those pods to...

@houshengbo I think the operator should set `maxUnavailable` to `1` as a sensible default (roll each of these critical components one at a time). And continue to allow the user...

Yes and no. Max unavailable would be set for serving I think. But if you're configuring HA it would make sense that the operator creates a PDB so that HA...

Still a problem