smi-spec
emissary
smi-spec | emissary | |
---|---|---|
12 | 14 | |
1,047 | 4,279 | |
- | 0.4% | |
2.7 | 8.1 | |
7 months ago | 7 days ago | |
Makefile | Python | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
smi-spec
-
A Comprehensive Guide to API Gateways, Kubernetes Gateways, and Service Meshes
The Service Mesh Interface (SMI) specification was created to solve this portability issue.
-
Service Mesh Use Cases
> I suspect if a Service Mesh is ultimately shown to have broad value, one will make it's way into the K8S core
I'm not so sure. I suspect it'll follow the same roadmap as Gateway API, which it already kind of is with the Service Mesh Interface (https://smi-spec.io/)
-
Service Mesh Considerations
It is very common that a service mesh deploys a control plane and a data plane. The control plane does what you might expect; it controls the service mesh and gives you the ability to interact with it. Many service meshes implement the Service Mesh Interface (SMI) which is an API specification to standardize the way cluster operators interact with and implement features.
-
Kubernetes: Cross-cluster traffic scheduling - Access control
Before we start, let's review the SMI Access Control Specification. There are two forms of traffic policies in osm-edge: Permissive Mode and Traffic Policy Mode. The former allows services in the mesh to access each other, while the latter requires the provision of the appropriate traffic policy to be accessible.
-
Announcing osm-edge 1.1: ARM support and more
osm-edge is a simple, complete, and standalone service mesh and ships out-of-the-box with all the necessary components to deploy a complete service mesh. As a lightweight and SMI-compatible Service Mesh, osm-edge is designed to be intuitive and scalable.
- KubeCon 2022 - Jour 1
-
Kubernetes State Of The Union — KubeCon 2019, San Diego
I started on Monday, attending ServiceMeshCon2019. My guesstimate is that about 1000 people attended it. I believe Service Mesh is playing such a crucial role in scaling cloud native technologies that large scale cloud-native deployments may not be possible without service mesh. Just like you cannot really succeed in deploying a microservices based application without a microservices orchestration engine, like Kubernetes, you cannot scale the size and capacity of a microservices-based application without service mesh. That’s what makes it so compelling to see all the service mesh creators — Istio, Linkerd, Consul, Kuma — and listen to them. There was also a lot of discussion of SMI (Service Mesh Interface) — a common interface among all services mesh. The panel at the end of the day included all the major service mesh players, and some very thought provoking questions were asked and answered by the panel.
-
GraphQL - Usecase and Architecture
Do you need a Service Mesh?
-
Introducing the Cloud Native Compute Foundation (CNCF)
In the episode with Annie, she gave a great overview of the CNCF and a handful of projects that she's excited about. Those include Helm, Linkerd, Kudo, Keda and Artifact Hub. I gave a bonus example of the Service Mesh Interface project.
-
Service Mesh Interface
SMI official website: https://smi-spec.io
emissary
-
Securing Front-end Applications in Kubernetes with SSL/TLS
We will install Ambassador Gateway which is an open-source Kubernetes-native API gateway for microservices. We will use it as a reverse proxy to manage external access to services within our Kubernetes cluster.
-
Building event-driven API services using CQRS, API Gateway and Serverless
Command and Query services APIs can be managed via lightweight, independently deployable, and scalable API gateways that can run anywhere that allow developers to manage API endpoints. They can handle extremely large volumes, as they run on highly scalable platforms, for example, Apache APISIX, Kong, Tyk, and Ambassador to name a few.
-
What are the most popular ingress controllers
Ambassador
-
3 Proven Ways Managers Can Improve Developer Focus
Did you know that it takes 23 minutes to get into a flow state? For some people it takes even longer. That means that for every question, disruption, email, and interruption that you or your coworkers are subjected to, it could be half an hour of productivity down the drain. We talked to Katie Wilde, VP of Engineering at Ambassador Labs, about how she manages workflow
-
How do you Integrate Emissary Ingress with OPA
Let's dive deep and start understanding more bit about Emissary Ingress.
-
Kubernetes Ingress, which one is the "best" and why?
Emissary is pretty much the gold standard for people with complicated setups: https://github.com/emissary-ingress/emissary
-
How to Reclaim Your Dev Team’s Focus w/ Ambassador Labs' Katie Wilde
Katie Wilde, VP of Engineering at Ambassador Labs, knows your pain and she’s on a crusade to help devs everywhere reclaim their focus.
-
The Kubernetes Ingress Concept and Ingress Controller (Part 1)
Ambassador API Gateway is an Envoy-based ingress controller.
-
Does anyone use emissary-ingress in production?
I am starting to doubt their marketing materials about broad adoption, because we cannot get it to work even with basic setup. Apart from terrible DX (e.g. you can provide whatever arbitrary configs, there is no validation), we keep hitting bug after bug after bug. They are not small bugs either, e.g. broken redirects. Any time I try asking questions in their Slack, their sales rep will message asking to "connect via zoom meeting to cover the pricing".
-
Exploring and Tech – Internationally Awesome with Peter ONeill
Peter: Yeah. So that was my first time having a DevRel title. I was a developer Advocate for Ambassador Labs, another startup. And so I think they were Series B at the time. They were centered around the developer experience. So I had a lot of fun diving into the DevRel industry with them. And so my manager that I was working for has a long history of DevRel. And so I got to learn a lot of tips and tricks from him.
What are some alternatives?
cni - Container Network Interface - networking for Linux containers
ingress-nginx - Ingress-NGINX Controller for Kubernetes
cloudwithchris.com - Cloud With Chris is my personal blogging, podcasting and vlogging platform where I talk about all things cloud. I also invite guests to talk about their experiences with the cloud and hear about lessons learned along their journey.
apisix - The Cloud-Native API Gateway
pipy - Pipy is a programmable proxy for the cloud, edge and IoT.
kubernetes-ingress - HAProxy Kubernetes Ingress Controller
osm-edge - osm-edge is a lightweight service mesh for the edge-computing. It's forked from openservicemesh/osm and use pipy as sidecar proxy.
gloo - The Feature-rich, Kubernetes-native, Next-Generation API Gateway Built on Envoy
kubefed - Kubernetes Cluster Federation
Ory Oathkeeper - A cloud native Identity & Access Proxy / API (IAP) and Access Control Decision API that authenticates, authorizes, and mutates incoming HTTP(s) requests. Inspired by the BeyondCorp / Zero Trust white paper. Written in Go.
envoy - Cloud-native high-performance edge/middle/service proxy
gRPC - The C based gRPC (C++, Python, Ruby, Objective-C, PHP, C#)