cyrus-mc

> We cannot revert the choice of using an annotation for this. Such a change would not be backwards compatible. I get the backwards compatibility but you could have a...

Experiencing this issue as well; The oddity is it only fails during an actual docker build. If I exec into the intermediate container just prior to the RUN tests command...

Still and issue for me. Would be nice to have this fixed.

This is due to the fact that `HTTPSPROXY` is set to `proxyProtocolStack` [ "TLS", "PROXY", "HTTP", "TCP" ] which generates configuration: ``` "listener_filters": [ { "name": "envoy.filters.listener.tls_inspector" }, { "name":...

The work around for now is to not set the `protocol` too `HTTPSPROXY` but rather explicitly set the `protocolStack` as shown above. However the documentation seems to point people to...

Based on conversation in community slack channel it appears that maybe different LB wrap TLS before proxy. I know with Ambassador 1.9 the order of the listeners was always `proxy_protocol`...

Reading the [RFC](https://www.haproxy.org/download/1.8/doc/proxy-protocol.txt) ``` In both cases, the protocol simply consists in an easily parsable header placed by the connection initiator at the beginning of each connection ``` This to...

@yiranwang52 I assume due to the label changes and title update that this is currently not a supported feature?

> I didn't know docker support this usecase. It's not supported right now, we will look into it. Thanks. Hopefully it is a feature that arrives soon. I was really...

This feature still hasn't been made available in makisu?