k3s
pipy-demos
k3s | pipy-demos | |
---|---|---|
7 | 4 | |
15,937 | 10 | |
- | - | |
9.2 | 7.9 | |
about 3 years ago | 11 days ago | |
Go | C | |
Apache License 2.0 | 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.
k3s
-
Kubernetes: Multi-cluster communication with Flomesh Service Mesh (Part 2)
In this demo, we will be using k3d a lightweight wrapper to run k3s (Rancher Lab’s minimal Kubernetes distribution) in docker, to create 4 separate clusters named control-plane, cluster-1, cluster-2, and cluster-3 respectively.
-
Pipy: Protecting Kubernetes Apps from SQL Injection & XSS Attacks
To run the demo locally, we recommend k3d a lightweight wrapper to run k3s (Rancher Lab’s minimal Kubernetes distribution) in docker.
-
When a node goes down, how long should k8s wait before migrating pods to other nodes?
I've been messing around with k8s (k3s) lately, and got to the "issue" of downtime/inconsistencies caused by one of multiple workers being down, who had pods running on them. I found a couple useful parameters here that helped me reduce the time needed to redeploy the old pods on other nodes, as well as stop sending requests to the NotReady node. But that got me thinking, how long should k8s wait before doing these things? Or is there perhaps a better option for increasing avaliability?
-
Kubernetes Development Environments – A Comparison
Local Kubernetes clusters are clusters that are running on the individual computer of the developer. There are many tools that provide such an environment, such as Minikube, microk8s, k3s, or kind. While they are not all the same, their use as a development environment is quite comparable.
-
Local Cluster vs. Remote Cluster for Kubernetes-Based Development
Since the developer is the only one who has to access this cluster for development, local clusters can be a feasible solution for this purpose. Over time, several solutions have emerged that are particularly made for running Kubernetes in local environments. The most important ones are Kubernetes in Docker (kind), MicroK8s, minikube and k3s. For a comparison of these local Kubernetes options, you can look at this post.
-
Kubernetes: Virtual Clusters As Development Environments
With local Kubernetes environments such as minikube or k3s, developers can create their own Kubernetes clusters on their local computers. This often leads to developers struggling with the management and setup of these pared-down Kubernetes technologies that are also not completely realistic compared to “real-world”, cloud-based environments. The upside of this approach is that the developers have full control over their environment and can independently create it whenever they need it.
-
[Recap] The API Hangout #31
K3d - a lightweight wrapper to run k3s in docker.
pipy-demos
-
Writing a DNS proxy with Pipy
Next, we will demonstrate how to use Pipy to implement a DNS proxy (more accurately, a combination of a proxy and a server) that returns DNS query requests from custom records. At the same time, we will also add a feature to return different DNS records based on the client IP address to achieve intelligent route resolution. The scripts used in the demonstration can be downloaded from here.
-
Pipy: Protecting Kubernetes Apps from SQL Injection & XSS Attacks
The demo source code is available on GitHub and can be downloaded from pipy-sqli-demo repository.
-
MQTT policy enforcement with Pipy
Sample policy and rules are defined in policy.json where we define 4 test accounts and some rules on which clients are allowed to subscribe/publish to which topics. Pipy proxy script will read this configuration file and enforce them before routing traffic to the upstream MQTT server. Refer to Publisher workflow and Subscriber workflow.
-
Pipy + Redis + Sentinel = High available Redis
Full source of demo is available and can be downloaded from https://github.com/flomesh-io/pipy-demos/tree/main/pipy-redis-sentinel
What are some alternatives?
minikube - Run Kubernetes locally
pipy - Pipy is a programmable proxy for the cloud, edge and IoT.
devspace-plugin-loft - Loft Plugin for DevSpace - adds commands like `devspace create space` or `devspace create vcluster` to DevSpace
cilium - eBPF-based Networking, Security, and Observability
multi-tenancy - A working place for multi-tenancy related proposals and prototypes.
kubefwd - Bulk port forwarding Kubernetes services for local development.
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.
k3v - Virtual Kubernetes
k3d - Little helper to run CNCF's k3s in Docker
microk8s - MicroK8s is a small, fast, single-package Kubernetes for developers, IoT and edge. [Moved to: https://github.com/canonical/microk8s]
kind - Kubernetes IN Docker - local clusters for testing Kubernetes