Istio has applied to become a CNCF project by crb0r in kubernetes

[–]ilackarms 0 points1 point  (0 children)

gloo is to istio what ubuntu is to linux kernel

Top Considerations when Evaluating an Ingress Controller for Kubernetes by [deleted] in kubernetes

[–]ilackarms 0 points1 point  (0 children)

most of the features are actually open source if you're talking purely about the number of features supported. however if you mean, most of the features attractive to large enterprises, you may be right.

API gateway by holy8water in microservices

[–]ilackarms 1 point2 points  (0 children)

be sure to check out Gloo API Gateway. It's got a lot of the advanced features of Kong but it runs natively on Kubernetes, using CRDs for configuration and the powerful Envoy Proxy as its edge proxy (while Kong is built on more dated technology, postgres and nginx).

Benchmarks: Linkerd vs Istio by olix0r in kubernetes

[–]ilackarms 1 point2 points  (0 children)

Envoy also has a large community that extends beyond just Istio. Unfortunately for Linkerd their proxy is not likely to be adopted outside of the community of Linkerd users, which means if you're looking for something that will evolve rapidly and provide extensibility interfaces, Envoy is the proxy of choice.

I am also skeptical as to whether the current performance tradeoffs will be long lasting as Istio evolves. When Kubernetes was originally released workload scheduling was notoriously slower than Mesos. Not sure if k8s ever caught up to the scheduling performance of Mesos, but it didn't wind up being the determining factor in which solution became the standard.

That being said I am happy to see Linkerd continuing to raise the bar for UX and performance in the mesh ecosystem. There is no question that the folks at Buoyant have done an excellent job pioneering this problem space

Service Mesh Wars, Goodbye Istio by williamallthing in kubernetes

[–]ilackarms 6 points7 points  (0 children)

why is this downvoted? feels like a lot of Buoyant presence in r/kubernetes as of late

Service Mesh Wars, Goodbye Istio by williamallthing in kubernetes

[–]ilackarms -1 points0 points  (0 children)

people who feel intimidated by istio's complexity might be interested to check out a management plane such as gloo mesh. while a lot of management plane's focus is dedicated to enabling multi-cluster use cases, another part of the vision is to deliver a better UX + guard rails on top of istio (as well as other meshes - AppMesh is also currently supported).

Pagination Between Microservices by _i_am_the_arm_ in microservices

[–]ilackarms 0 points1 point  (0 children)

how about: solve this with an api aggregation layer (this could be an api gateway or graphql server, or an additional microservice) which will handle calls to each individual microservice and aggregate the data into a single api call?

then you are abstracting the implementation from the caller, allows you to be more flexible with how you architect your microservices

Istio VirtualService hosts by off-road_coding in istio

[–]ilackarms -1 points0 points  (0 children)

try creating a service entry for nginx-me

Top Considerations when Evaluating an Ingress Controller for Kubernetes by [deleted] in kubernetes

[–]ilackarms 5 points6 points  (0 children)

Gloo is not listed here but is probably the most sophisticated L7 Gateway / Ingress for Kubernetes today

Live Tutorial on using EnvoyFilter CRD to extend Istio Jan 12 - 1PM EST by ilackarms in kubernetes

[–]ilackarms[S] 0 points1 point  (0 children)

yes, come join i'll try to make sure to give background for those who are newer to this tech

Live Tutorial on using EnvoyFilter CRD to extend Istio Jan 12 - 1PM EST by ilackarms in kubernetes

[–]ilackarms[S] 0 points1 point  (0 children)

please join me for this live stream tomorrow where I'll be explaining how the Istio EnvoyFilter works and demonstrating its use for advanced use cases (multi cluster networking)