osm
gateway-api
osm | gateway-api | |
---|---|---|
7 | 29 | |
2,586 | 1,572 | |
- | 2.7% | |
8.9 | 9.8 | |
10 months ago | 3 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.
osm
-
Service Mesh Considerations
If you'd like to go a bit deeper into service mesh technology, be sure to check out the resources listed below then head over to the Open Service Mesh with Azure Kubernetes Service lab to get hands-on and see a service mesh in action! Open Service Mesh is an open-source, lightweight service mesh that is easy to install and operate, so I encourage you to take it for a spin 🚀
-
osm-edge: Using access control policies to access services with the service mesh
osm-edge forked from Open Service Mesh is a lightweight, extensible, cloud-native, SMI-compatible service mesh built purposely for Edge computing. osm-edge uses lightweight programmable proxy Pipy as a sidecar proxy.
-
Benchmarking osm and osm-edge data planes
osm-edge is built on top of Open Service Mesh (OSM) v1.1.0 codebase and is a lightweight service mesh for resource-sensitive cloud environments and edge computing scenarios. It uses osm as the control plane and Pipy as the data plane and features high performance, low resources, simplicity, ease of use, scalability, and compatibility (x86/arm64 support).
-
Announcing osm-edge 1.1: ARM support and more
osm-edge is a fork of open service mesh and we will strive to keep this fork in sync with its upstream and propose back major changes and/or feature proposals to upstream for broader benefits of the community. Both OSM and osm-edge are hosted on Github. If you have any feature request, question, or comment, we’d love to have you join the rapidly-growing community via Github Issues, Pull Requests, or osm slack channel!
-
Need to create a simple POC to prove that mTLS is being used for service to service communication in AKS with Open Service Mesh
Link: https://github.com/openservicemesh/osm/issues/4840
-
Azure Weekly Updates - 21st May 2022 - Part 2
Azure Arc-enabled Kubernetes allows us to attach and configure Kubernetes clusters running anywhere. Open Service Mesh (OSM) is a lightweight, extensible, Cloud Native service mesh that allows users to uniformly manage, secure, and get out-of-the-box observability features for highly dynamic microservice environments. The Open Service Mesh (OSM) extension is a managed service mesh for Arc-enabled Kubernetes clusters that is lightweight and extensible.
-
Pull Requests Like a PRO: Tips to Make High-Quality Pull Requests
Pull Request template from the Open Service Mesh project
gateway-api
-
ArgoCD Deployment on RKE2 with Cilium Gateway API
It has already been a couple of years since the Kubernetes Ingress was defined as a “frozen” feature while further development will be added to the Gateway API.
-
A Comprehensive Guide to API Gateways, Kubernetes Gateways, and Service Meshes
Kubernetes provides two APIs to achieve this, the Ingress API and the Gateway API.
-
Using k8s-apiserver as AAA server for microservices?
With all that said, K8s is not really meant to function as an API gateway to arbitrary services. You should look into API gateways such as NGINX, Kong or others, service meshes as others have already pointed out, or have a look at the K8s Gateway API the SIG is currently working on. The last one is in the early stages of adoption, but it could provide you with a nice way to do an API Gateway right in K8s.
-
load balancer and kubernetes
Maybe there's something in the new fangled gateways.
-
Service Mesh Considerations
Keep an eye on the Gateway API GAMMA Initiative as it is currently evolving with the goal of streamlining how services meshes can implement the Gateway API and reduce some overlap.
- EKS: is it possible to rewrite the URL with ALB?
-
Apache Apisix: Open-Source API Gateway and API Management Platform
The selling point for me was ability to configure it using Kubernetes CRD's and future support of the Gateway API (under development - <https://gateway-api.sigs.k8s.io/>).
Developers can version their API now within helm charts or even yaml templates held along the code in their repositories.
-
A quick glance at the Kubernetes Gateway API
-- https://gateway-api.sigs.k8s.io
-
Sharing load balancers between containers
While you're learning about ingresses, also look into the k8s Gateway API, which is the next generation. https://gateway-api.sigs.k8s.io/
-
Exposing k8s services
The GatewayAPI model is quite different from the LB/ingress model, in the cluster it consists of gateway and route objects. Once the gateway is created routes connecting gateways to services are added. If you need to change how requests are distributed, the routes are updated but the gateway remains so the address and other configuration remains consistent. Gateways can be shared by multiple routes. Take a look at https://gateway-api.sigs.k8s.io/ its a bit terse but you will get the picture.
What are some alternatives?
istio - Connect, secure, control, and observe services.
caddy-l4 - Layer 4 (TCP/UDP) app for Caddy
geo-golang - Go library to access geocoding and reverse geocoding APIs
apisix-opa-plugin
kuma - 🐻 The multi-zone service mesh for containers, Kubernetes and VMs. Built with Envoy. CNCF Sandbox Project.
kubernetes-ingress-controller - :gorilla: Kong for Kubernetes: The official Ingress Controller for Kubernetes.
pipy - Pipy is a programmable proxy for the cloud, edge and IoT.
tyk-operator - Tyk Operator for Kubernetes
pbf - OpenStreetMap PBF golang parser
OPA (Open Policy Agent) - Open Policy Agent (OPA) is an open source, general-purpose policy engine.
meshery - Meshery, the cloud native manager
multus-cni - A CNI meta-plugin for multi-homed pods in Kubernetes