pipy
k3d
pipy | k3d | |
---|---|---|
27 | 76 | |
710 | 5,079 | |
2.4% | 1.0% | |
9.8 | 8.4 | |
3 days ago | 13 days ago | |
C++ | Go | |
GNU General Public License v3.0 or later | MIT License |
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.
pipy
- PIPY: New programmable network proxy general available
-
Pipy proxy: Creating HTTP Tunnel with 10 lines of code
Pipy is an open-source, lightweight, high-performance, modular, programmable, cloud-native network stream processor that is ideal for a variety of use cases ranging from (but not limited to) edge routers, load balancers & proxy solutions, API gateways, static HTTP servers, service mesh sidecars, and other applications. Previously we have covered several use cases, and in this blog post will continue our learning of Pipy by implementing an HTTP Tunnel functionality by only using the PipyJS scripting language.
-
Kubernetes: Multi-cluster communication with Flomesh Service Mesh (Part 2)
If you are interested in learning more about SMI-compatible Service Mesh, FSM, and Programmable Proxy, visit our website Flomesh.io for more detailed documentation, tutorials, and use cases.
-
Pipy: Protecting Kubernetes Apps from SQL Injection & XSS Attacks
But as the complexity of your apps and architecture grows, you might require more fine–grain control over your services. And if your organization requires Zero Trust and has a need for end–to–end encryption like mTLS, you should consider a service mesh like osm-edge a light weight, ultra fast, low resources, highly extensible, Service Mesh Interface (SMI) compatible, built for edge and cloud computing service mesh. When you have communication between services (east–west traffic), a service mesh allows you to control traffic at that level.
-
Pipy 0.70.0 is released!
Below we list the most remarkable changes in the Core API and PipyJS. For a detailed change log, refer to Pipy Release Page
-
Flomesh Ingress Controller with Kubernetes Multi-tenancy
Flomesh Service Mesh(FSM) from Flomesh is Kubernetes North-South traffic manager, provides Ingress controllers, Gateway API, Load Balancer, and cross-cluster service registration and service discovery. FSM uses Pipy - a programmable network proxy, as its data plane and is suitable for cloud, edge, and IoT.
-
Using FSM Ingress controller with osm-edge service mesh
FSM is another open-source product from Flomesh for Kubernetes north-south traffic, gateway api contoller, and multi-cluster management. FSM uses Pipy, a programmable proxy at its core, and provides an Ingress controller, Gateway API controller, load balancer, cross-cluster service registration discovery, and more.
-
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
We're very happy to announce the release of osm-edge 1.1. This release is the culmination of months of effort from the flomesh.io team and we are very excited to unveil it today. osm-edge is built on top of Open Service Mesh v1.1.0 codebase and is built purposely for edge computing and uses lightweight, high-performant, cloud native, and programmable proxy Pipy as its data plane and sidecar proxy.
-
Pipy 0.50.0 is released!
Below we list the most remarkable changes in the Core API and PipyJS. For detailed change log refer to Pipy Release Page
k3d
-
15 Options To Build A Kubernetes Playground (with Pros and Cons)
K3D: is a lightweight distribution of Kubernetes designed for resource-constrained environments. It is an excellent option for running Kubernetes on virtual machines or cloud servers.
-
Why You Should Use k3d for Local Development. A Developer's Guide
k3d is a lightweight wrapper that makes running Kubernetes (specifically, the lightweight k3s distribution) in Docker straightforward and efficient. It's designed to provide developers with a quick and easy way to test Kubernetes without the overhead of setting up a full cluster.
- Turning my laptop into a one-node k8s-cluster?
- Single node K8S distribution for little production
-
Distributing containers to run locally?
If you customer prefers to run the standard docker engine you could use k3d
-
Unable to launch older version (v2.6.8) of Rancher
You don’t need to run Rancher from a Kubernetes cluster, the rancher/rancher image works fine with Docker (it uses k3d, aka « k3s in docker » : https://k3d.io/).
- Blog: KWOK: Kubernetes WithOut Kubelet
-
Building a RESTful API With Functions
K3d and Skaffold for local development
-
Local Kubernetes Playground Made Easy
If you are a developer and want to learn how to deploy applications to a cluster, getting a cluster up an running can be a daunting task in it's own rights. There are many ways to do it: spinning up local virtual machines and configuring from scratch or using tools like minikube, etc. You may not care for the pain of setting up and configuring a cluster, and if that is you, then the quickest way that I have found is using k3d.
- Despliega un clúster de Kubernetes en segundos con k3sup
What are some alternatives?
osm - 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.
kind - Kubernetes IN Docker - local clusters for testing Kubernetes
forward-proxy - Minimal HTTP(S) forward proxy using 150LOC and only standard libraries.
lima - Linux virtual machines, with a focus on running containers
smi-spec - Service Mesh Interface
k0s - k0s - The Zero Friction Kubernetes
fsm - Lightweight service mesh for Kubernetes East-West and North-South traffic management, uses ebpf for layer4 and pipy proxy for layer7 traffic management, support multi cluster network.
k3sup - bootstrap K3s over SSH in < 60s 🚀
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.
k3s - Lightweight Kubernetes
pipy-demos - Central repository for Pipy demos
microk8s - MicroK8s is a small, fast, single-package Kubernetes for datacenters and the edge.