liqo
ingress-nginx
liqo | ingress-nginx | |
---|---|---|
18 | 203 | |
1,042 | 16,754 | |
2.7% | 1.2% | |
9.6 | 9.6 | |
5 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.
liqo
-
Questions for Heroku-like Project
I suggest examining liqo which allows you to peer clusters with each other. Might be what you're looking for: https://www.cncf.io/blog/2021/04/12/simplifying-multi-clusters-in-kubernetes/
-
Déployer et exposer globalement une application multi-clusters via K8GB et Liqo …
Liqo
- Can I run a wireguard VPN as a sidecar or a service available to my containers?
-
centralized control plane for multiple GKE clusters
Maybe liqo? https://liqo.io/
-
Cross-cloud Kube? AWS App Mesh?
Liquo is another good one. https://liqo.io/
-
Best approach for treating multiple clusters as a single cluster?
Do you have a simple comparison between this and https://liqo.io/?
-
Benchmarking a Pi cluster with HPL (like the Top500 supercomputer list)
I am watching this https://liqo.io/ project that can create endless Kubernetes cluster on top of the decentralized infrastructure. They use Wireguard tunnel for inter nodes/clustering networking
-
Connecting nodes in isolated networks
To be honest, you might have a better chance at creating a multi-cluster setup, with a solution like Liqo (https://liqo.io/). I never used this, but it's supposed to join multiple clusters in a way that you can control all of them from one primary master.
- Weekly: Questions and advice
- Show HN: Liqo v0.3 – Build a K8s super-cluster
ingress-nginx
-
Automating EKS Deployment and NGINX Setup Using Helm with AWS CDK in Python
# Add NGINX ingress using Helm eks.HelmChart( self, "NginxIngress", cluster=cluster, chart="ingress-nginx", repository="https://kubernetes.github.io/ingress-nginx", namespace="ingress-nginx", values=helm_values )
-
deploying a minio service to kubernetes
ingress-nginx
-
Upgrading Hundreds of Kubernetes Clusters
The second one is a combination of tools: External DNS, cert-manager, and NGINX ingress. Using these as a stack, you can quickly deploy an application, making it available through a DNS with a TLS without much effort via simple annotations. When I first discovered External DNS, I was amazed at its quality.
-
[06/52] Accessible Kubernetes with Terraform and DigitalOcean
resource "helm_release" "icrelease" { name = "nginx-ingress" repository = "https://kubernetes.github.io/ingress-nginx" chart = "ingress-nginx" version = "4.9.1" namespace = kubernetes_namespace.icnamespace.metadata[0].name set { name = "controller.ingressClassResource.default" value = "true" } }
-
Deploy Ghost with MySQL DB replication using helm chart
helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx helm repo update helm upgrade --install ingress-nginx ingress-nginx/ingress-nginx --namespace ingress-nginx --create-namespace -f custom/ghost/nginx.yaml
-
Kubernetes Gateway API v1.0: Should You Switch?
For example, if you chose Nginx Ingress, you will use some of its dozens of annotations that are not portable if you decide to switch to another Ingress implementation like Apache APISIX.
- nginx ingress controller installation
-
IP-Whitlisting: Is adjusting nginx-ingress-controller service a solution?
The controller is installed with helm upgrade --install ingress-nginx ingress-nginx --repo https://kubernetes.github.io/ingress-nginx --namespace ingress-nginx --create-namespace
-
Deploy Rancher on AWS EKS using Terraform & Helm Charts
helm repo add jetstack https://charts.jetstack.io helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx helm repo add rancher-latest https://releases.rancher.com/server-charts/latest helm repo update helm repo list
-
☸️ Kubernetes NGINX Ingress Controller: 10+ Complementary Configurations for Web Applications
Everything in the YAML snippets below — except for ingress configuration — relates to configuring the NGINX ingress controller. This includes customizing the default configuration.
What are some alternatives?
turing-pi-2-cluster - DEPRECATED - Turing Pi 2 Cluster
traefik - The Cloud Native Application Proxy
k0s - k0s - The Zero Friction Kubernetes
emissary - open source Kubernetes-native API gateway for microservices built on the Envoy Proxy
microk8s - MicroK8s is a small, fast, single-package Kubernetes for datacenters and the edge.
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
k8s-gitops - Kubernetes cluster powered by GitOps with FluxCD- Unified source of truth, automated workflows, declarative infrastructure, and cutting-edge DevOps practices.
cilium-cli - CLI to install, manage & troubleshoot Kubernetes clusters running Cilium
microk8s - MicroK8s is a small, fast, single-package Kubernetes for developers, IoT and edge. [Moved to: https://github.com/canonical/microk8s]
haproxy-ingress - HAProxy Ingress
k3s-rpi-cluster - Setting up a K3S Kubernetes cluster using RPI4
application-gateway-kubernetes-ingress - This is an ingress controller that can be run on Azure Kubernetes Service (AKS) to allow an Azure Application Gateway to act as the ingress for an AKS cluster.