gloo
opa-envoy-plugin
| gloo | opa-envoy-plugin | |
|---|---|---|
| 3 | 3 | |
| 3,984 | 306 | |
| 0.5% | 0.7% | |
| 9.5 | 8.4 | |
| 5 days ago | 10 days ago | |
| Go | Go | |
| 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.
gloo
-
How to choose the best versioning mechanism?
A similar approach can be seen here: solo.io/gloo
-
Releasing Gloo 0.4.0
Does it bug anyone else when people come out promoting their "new" thing that has used the name of an existing well established thing? https://github.com/solo-io/gloo like... how hard is it to search and see the name's already taken?
-
Monthly Who Is Hiring
We are a small but rapidly growing startup developing cutting edge Service Mesh and API Gateway solutions for a sizable list of production customers. We are known in the community for our open source API Gateway and service mesh management plane as well as our enterprise product offerings.
opa-envoy-plugin
- Authorization for synchronous communication between services
-
How do you Integrate Emissary Ingress with OPA
Open Policy Agent is a well-known general-purpose policy engine and has emerged as a policy enforcer across the stacks be it API gateways, service meshes, Kubernetes, microservice, CICD, or IAC. OPA decouples decision making from policy enforcement such that whenever your software needs to make a decision regarding the incoming requests, it queries OPA. OPA-Envoy extends OPA with a gRPC server that implements the Envoy External Authorization API, thus making itself compatible to be as an external authz server to Emissary.
-
OPA + Istio/Envoy: ConfigMap
I'm observing the quick_start.yaml provided by OPA and trying to comprehend what's happening in the inject.rego resource (proper name?) under the ConfigMap. Can anyone break it down for me a bit? I think I have an inkling of what's happening but not sure.
What are some alternatives?
emissary - open source Kubernetes-native API gateway for microservices built on the Envoy Proxy
cerbos - Cerbos is the open core, language-agnostic, scalable authorization solution that makes user permissions and authorization simple to implement and manage by writing context-aware access control policies for your application resources.
apisix - The Cloud-Native API Gateway
gatekeeper - 🐊 Gatekeeper - Policy Controller for Kubernetes
grpc-health-probe - A command-line tool to perform health-checks for gRPC applications in Kubernetes and elsewhere
opal - Fork of https://github.com/permitio/opal
Kong - 🦍 The Cloud-Native API Gateway and AI Gateway.
OPA (Open Policy Agent) - Open Policy Agent (OPA) is an open source, general-purpose policy engine.
mizu - The API traffic viewer for Kubernetes providing deep visibility into all API traffic and payloads going in, out and across containers and pods inside a Kubernetes cluster. Think TCPDump and Wireshark re-invented for Kubernetes [Moved to: https://github.com/kubeshark/kubeshark]
Ory Hydra - OpenID Certified™ OpenID Connect and OAuth Provider written in Go - cloud native, security-first, open source API security for your infrastructure. SDKs for any language. Works with Hardware Security Modules. Compatible with MITREid.
gloo - Collective communications library with various primitives for multi-machine training.
kuma - 🐻 The multi-zone service mesh for containers, Kubernetes and VMs. Built with Envoy. CNCF Sandbox Project.