We are live NOW with @linsun_unc@gihanson and @kfekete to talk about #Istio Ambient Mesh and what it means for your wallet >> https://t.co/hw98tmYvp1
What does #Istio Ambient Mesh mean for your wallet? Join the Solo Hoot livestream tomorrow at 7AM PT / 10AM ET with @linsun_unc@gihanson and @kfekete >> https://t.co/nLFkwvMdc3
EXCELLENT blog by my colleagues @kfekete@gihanson covering the cost savings of the new @IstioMesh Ambient Mesh architecture https://t.co/52QKtBCTMp with a repo to reproduce results @soloio_inc#ambientmesh
This is the right path forward. Sidecars have always been an unfortunate implementation detail. Mesh features can/will move into the underlying infra. Excited to see how this evolves and very excited to see Envoy further abstracted from the average user.
Join @gihanson for his talk at #IstioCon where he'll cover common pitfalls in egress configurations and debugging techniques for when calls to external databases start failing.
Join us! https://t.co/pukwQuV29S
@yaofei@KialiProject If it’s built on top of https://t.co/NoQMI381h5, Engarde doesn’t support custom access log formats outside of Envoy and Istio’s defaults. I did something similar as well for parsing Istio access logs: https://t.co/jKXuvw1nRj
Seems appropriate to wear my new @EnvoyProxy hoodie today, looking forward to discuss debug Envoy in 2 hours with @djannot and @gihanson@soloio_inc#hoot:
https://t.co/5JSotiYqkF
Happy to have yet another founding member of the @IstioMesh community join @soloio_inc !! Today we welcome @gihanson to our OSS team. Greg's tenure with #Istio starts all the way back to the Amalgam8 project (the OSS pre-cursor to Istio!). Welcome, Greg!!!
Loved this! @IstioMesh helped IBM App Connect team to understand interactions with external systems and bugs with their code! From Greg Hanson @martinross83 #servicemeshcon2019
Interesting insight into the @IBM App Connect journey with @IstioMesh, via Greg Hanson at #servicemeshcon2019
12 months+ project, they're in prod, but not with all features enabled. Ingress was also tricky ("ingress is often org/env specific")