kube-vip
kuma
kube-vip | kuma | |
---|---|---|
4 | 5 | |
1,842 | 3,519 | |
4.5% | 1.3% | |
9.3 | 9.9 | |
8 days ago | 4 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.
kube-vip
-
US-16-150W: DOT1S role changing from ROLE_DESIGNATED to ROLE_DISABLED
I am running a US-16-150W (firmware 6.3.13) with three Proxmox nodes connected (along with other stuff and an USG upstream). Everything is connected with CAT6. On each physical Proxmox node are two VMs, a K8s master and a K8s worker node. On the cluster I am running Longhorn. The cluster is using [kube-vip](https://github.com/kube-vip/kube-vip) for HA control plane (in BGP mode) and exposing load balancers.
-
1 CPU per kubernetes node?
Look into kube-vip. Virtual IP for your control planes. Saves you the resources of having to run a separate VM to load balance them.
- kube-vip/kube-vip: Kubernetes Control Plane Virtual IP and Load-Balancer
- Suggestions for load balancer setup
kuma
-
Any new Opensource projects in (go) looking for contributors. I want to start my journey as an OSS contributor.
https://github.com/kumahq/kuma is an CNCF OSS service mesh for Kubernetes and VMs. We're a control plane on top of Envoy proxy. Very actively developed project, some big adopters in the community, and we've just refreshed all of our Good First Issues.
-
Gotta love Kuma, thank you kind stranger making it !
And not just "Kuma" : https://github.com/kumahq/kuma
-
Powering Kubernetes in the Cloud with Kuma Service Mesh
Another important change to make is that when you create the cluster, change the Nodes in the "Default pool" to use the COS (not COS_CONTAINERD) image type. There are some underlying issues when using Kuma with GKE, as noted in this GitHub issue, and this is the currently recommended workaround. Otherwise, you will hit pod initializing issues that affect certificate provisioning.
-
How I Stopped Coding Repetitive Service Components with Kong
Taking things to a broader level, Kuma is another platform agnostic-OSS solution for service mesh and microservice management – with control plane support of Kubernetes, virtual machines (VM), and even bare-metal environments. Kuma was donated to the Cloud Native Computing Foundation (CNCF) by Kong and still actively contributes to the evolving code base.
-
Service Mesh - Introduction
Kuma Kuma, from Kong, prides itself on being a usable service mesh alternative. Kuma is a platform-agnostic control plane built on Envoy. Kuma provides networking features to secure, observe, route, and enhance connectivity between services. Kuma supports Kubernetes in addition to virtual machines.
What are some alternatives?
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
kubernetes-ingress-controller - :gorilla: Kong for Kubernetes: The official Ingress Controller for Kubernetes.
kube-router - Kube-router, a turnkey solution for Kubernetes networking.
kong-oidc-keycloak - Kong OIDC + Keycloak + httpbin
k3sup - bootstrap K3s over SSH in < 60s 🚀
konga - More than just another GUI to Kong Admin API
external-dns - Configure external DNS servers (AWS Route53, Google CloudDNS and others) for Kubernetes Ingresses and Services
kong-pongo - Tooling to run plugin tests with Kong and Kong Enterprise
raspberry-pi-kubernetes-cluster - Designs, instructions, and more for a seven node Raspberry PI Kubernetes cluster.
cubefs - cloud-native file store
k8gb - A cloud native Kubernetes Global Balancer
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.