ckwang

5 ms·

1.
by ckwang 8y ago
The "back" proxy was the initial setup with SmartStack, so we went with that for minimal viable first steps. We wanted to make incremental changes, changing as little as possible, for this migration so we could monitor for correct
2.
by ckwang 8y ago
We route all outbound traffic from internal services through Envoy, even if the destination isn't running Envoy. We don't have envoy running as a "front" proxy right now, i.e. our L4 setup isn't Envoy <-> Envo
3.
by ckwang 8y ago
Yes! HAProxy is a terrific piece of tech, and has been awesome for our use cases so far. We do quite a bit with it for our main ingress routing and it was basically flawless as our data plane in SmartStack. I'm really excited about wha
4.
by ckwang 8y ago
That's pretty close to our next immediate steps as well :)
5.
by ckwang 8y ago
We run one proxy per machine, even when there are multiple services running. The proxy is just an abstraction to the downstream dependencies. Even if there are multiple services per machine, they can still reach downstream services via the
6.
by ckwang 8y ago
Per-service proxy deployments are a bit complex for the infrastructure but provide a nice abstraction for the service and service developers themselves. The configuration scheme is indeed daunting, which is what we're hoping Envoy and
7.
by ckwang 8y ago
We're actually looking to put Envoy in front of the redesign stack at some point in the near future! The major services backing the redesign can be isolated into a few smaller pieces, and we'd like to have Envoy be a routing layer
8.
by ckwang 8y ago
We're currently evaluating the pieces that comprise Istio, both within Kubernetes and outside of it in our existing infrastructure. We didn't do so immediately because we did not want to immediately update all of our technology at
9.
by ckwang 8y ago
We have not yet put Envoy in our main HTTP ingress path, but internally we have designs and implementation paths ready to go, and it's definitely being considered for public ingress traffic. As we noted in the last "teaser" s
10.
by ckwang 8y ago
Let me start by saying: The gotchas that we've experienced have been far eclipsed by the benefits. Aside from what what discussed, there weren't many things with Envoy specifically. We did have a few minor issues with the Thrift t
11.
by ckwang 8y ago
1. We are considering Istio! This is especially true for our Kubernetes environment. We are already planning to deploy Pilot for the first iteration of our control plane in our non-K8s environment, so the other pieces that comprise Istio is
12.
by ckwang 8y ago
Hello! Blog post writer here. Happy to answer any questions.
13.
by ckwang 14y ago
It's odd to me too. They had a great deal of pre-order information, something that most other server teams that face crazy launches don't ever have. I would guess that they could at least estimate the load to an order of magnitude. The fact
14.
by ckwang 15y ago
I'm curious as to why you feel that way. Why is "harshing on frats" as you put it not a negative act? Also, how does the reddit post not apply to the original issue here?
15.
by ckwang 15y ago
"LOL @ Phi Delta Toolbag." I would think that's pretty offensive to anyone who's in any sort of "* Phi Delta *" fraternity. In a thread that touches on the offensiveness of stereotypes and subsequent alienation, the irony of both the commen
16.
by ckwang 15y ago
That's actually my lecture that ClassMetric broke down in the blog post. From a (first time) instructor's perspective, I don't see the tool as a distraction to students. I'm not punishing students for using it, and students have another way