Thomas

[Thomas @grampelberg]

@LachlanEvenson @MelanieCebula That’s the plan! I’m really looking forward to it

[Thomas @grampelberg]

@LachlanEvenson @MelanieCebula It is an unfortunate rumor :( I’m still in Portland living vicariously through the rest of y’all.

[Thomas @grampelberg]

I'll be in person at #KubeCon this year. Would really like to catch up if you're in town.

[Thomas @grampelberg]

@zingermans is your website down? I've been getting a "technical difficulties" page all week.

[Thomas @grampelberg]

Does anyone have an invite for @Levels ? Really interested in how my glucose changes over the day.

[Thomas @grampelberg]

Ever wonder what tradeoffs service meshes take during implementation? I have a chat with @mitchashimself and @CodingBeenz about how @Linkerd, @IstioMesh and Consul approach the tough problem of building usable, reliable products. https://t.co/cX3RKzUQTF

[Thomas @grampelberg]

Interested in getting multi-cluster kubernetes setup fast and easy? Check out my talk with @danielbryantuk from #KubeCon! We show how to do it with @Linkerd and @ambassadorlabs. If you have two clusters already, it shouldn't take more than 10 minutes =) https://t.co/UnQd5lFNls

[Sebastien Pahl @sebp]

My co-founder @matappelman and I finally went public with the startup we have been working on: https://t.co/IUZ8SeTZt5

An "Open Source Datadog": https://t.co/nUtSR8mRvx

This was a monumental effort by the team, I could not be prouder! Thank you!

[Keith @KeithMcC]

This was @grampelberg at 5% grumpiness - this is like a blue moon, a very rare occurrence, so check it out!

[Thomas @grampelberg]

Come check it out! I’ll be there chatting about multi-cluster and service meshes =)

[Ambassador @ambassadorlabs]

🚨Free t-shirt! We're kicking off Ambassador Fest in one week, and we want to see you there! 1) Retweet any of our #AmbassadorFest posts and tag us 2) Come to a session or office hours and share your Twitter handle 3) We'll connect you with a free t-shirt! https://t.co/wwSYtZxnLy

[Thomas @grampelberg]

Had a fantastic time chatting with the @KubernetesPod folks about all things service mesh and containers. Make sure to have a listen =)

https://t.co/a7Me1k5wZl

[Kubernetes Podcast from Google @KubernetesPod]

Thomas Rampelberg (@grampelberg) works on @Linkerd at @BuoyantIO and is an author of the @SMI_spec.

He joins us to explain service mesh, and what’s new in Linkerd 2.9. He also tells us about the birth and death of @DCOS.

📃 https://t.co/9zHclgc8Hz
🔊 https://t.co/WMJExlQBuc

[Thomas @grampelberg]

@3266miles With the upcoming 2.9 release, the header on ingress is no longer required as well (which means no more annotations!).

[Thomas @grampelberg]

@3266miles You only need one gateway though, there's no reason to use more than one unless you've got specific scaling requirements.

[Thomas @grampelberg]

@3266miles What do you mean by external interfaces and 1 service per ingress?

[Thomas @grampelberg]

@JeroenJacobs79 @Linkerd It doesn't work at all in the 2.8 release. We've got it working in the current edge and it'll be in upcoming 2.9 release.

[Thomas @grampelberg]

@ibuildthecloud @KubeSail Fetch works well enough, just needs a layer to do integration into something like react. I needed something that could actually stream responses (for watches) and stream responses (so that I didn't have to wait for the slowest cluster's response).

[Thomas @grampelberg]

@ibuildthecloud @KubeSail I'm dynamically generating subdomains - one for each watch.

[Thomas @grampelberg]

@ibuildthecloud @KubeSail Potentially as a teaser, I'm also doing it across multiple clusters in a single dashboard .... getting around the concurrent request limit in browsers so you can have multiple watches going against many k8s clusters was fun.

[Thomas @grampelberg]

@ibuildthecloud @KubeSail I've actually done it and am pretty happy with the result. I had to write a custom HTTP client to do it, but I've got full watches, queries, updates, whole 9 yards =)