flannel
ingress-nginx
Our great sponsors
flannel | ingress-nginx | |
---|---|---|
13 | 200 | |
8,460 | 16,522 | |
0.9% | 1.6% | |
8.7 | 9.6 | |
3 days ago | 6 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.
flannel
-
How to create a 3-node kubernetes cluster and deploy an application on my ubuntu 22.04 minibox
$ kubectl apply -f https://github.com/flannel-io/flannel/releases/latest/download/kube-flannel.yml
-
Kubernetes Setup With WSL Control Plane and Raspberry Pi Workers
--pod-network=10.244.0.0/16: This is the default CIDR for flannel, and also avoids a conflict with my internal network if calico is used (which is the plan)
-
Deploy Kubernetes (K8s) on Amazon AWS using mixed on-demand and spot instances
The installation of K8s id done by kubeadm. In this installation Containerd is used as CRI and flannel is used as CNI.
-
Fully automated Kubernetes (K8s) deployment on AWS using mixed on-demand and spot instances
K8s is installed through kubeadm ad uses Containerd as CRI and Flannel as CNI. You can also install longhorn for the persistent storage and nginx ingress controller for the ingress rules.
This terraform module will deploy a high available Kubernetes (K8s) cluster on Amazon AWS, using mixed on-demand and spot instances. K8s is installed through kubeadm ad usesContainerd as CRI and Flannel as CNI. You can also install longhorn for the persistent storage and nginx ingress controller for the ingress rules. Please note, this is only an example on how to Deploy a Kubernetes cluster. For a production environment you should use EKS or ECS.
-
K3S Calico networking Issues
I have Ubuntu 20.x and 21.x installed in my cluster, mostly because I am familiar with Ubuntu and figured the latest LTS versions would be a good idea to use for docker swarm and now kubernetes.... But there is a kernel bug, (k3s issue link and flannel issue link) with VXLAN that makes the default flannel container networking interface not work..... So I decided to Calico as the CNI to experiment with it, but I have been running to issues with BIRD is not ready: errors on only 2 of my nodes..... Which is an improvement then all of my nodes having the error like a couple of days ago.... but it is frustrating that only 2 have the error....
-
Kubernetes on VPN (WireGuard)
Flannel cni has a special requirement - it needs the k8s cluster to have a preassigned CIDR (see here). IDK how to do that in a live cluster, as I had run kubeadm reset a few times already and I saw no reason not to recreate my cluster one again. And so I did. And while I was recreating the cluster, I also had a great opportunity to specify the IP address I wanted the k8s API to be accessible through.
ingress-nginx
-
[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.
-
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
apiVersion: networking.k8s.io/v1 kind: Ingress metadata: annotations: # sticky session, from documentation: https://kubernetes.github.io/ingress-nginx/examples/affinity/cookie/ nginx.ingress.kubernetes.io/affinity: "cookie" nginx.ingress.kubernetes.io/affinity-mode: "persistent" # change to "balanced" (default) to redistribute some sessions when scaling pods nginx.ingress.kubernetes.io/session-cookie-name: "name-distinguishing-services" nginx.ingress.kubernetes.io/session-cookie-max-age: "172800" # in seconds, equivalent to 48h [...]
Everything in the YAML snippets below — except for ingress configuration — relates to configuring the NGINX ingress controller. This includes customizing the default configuration.
-
Implementing TLS in Kubernetes
helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx helm repo update helm install ingress-nginx ingress-nginx/ingress-nginx -f ingress-values.yaml
-
Apollo Backend just made public, "The goal of making the code for this repo available is to show that despite statements otherwise by Reddit...
Kubernetes alone is enough of an example. So are various cloud utilities used all around the world, such as ingress-nginx, cert-manager, traefik, Docker and countless others. Go is what smart modern web developers actually want to use to create great products. Everything else is what industry dinosaurs force them to use to make a living at big companies peddling trash.
-
Ingress controller for vanilla k8s
This: https://kubernetes.github.io/ingress-nginx/ Not this: https://docs.nginx.com/nginx-ingress-controller/
-
Unleash Your Pipeline Creativity: Local Development with Argo Workflows and MinIO on Minikube
helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
What are some alternatives?
traefik - The Cloud Native Application Proxy
emissary - open source Kubernetes-native API gateway for microservices built on the Envoy Proxy
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
cilium-cli - CLI to install, manage & troubleshoot Kubernetes clusters running Cilium
haproxy-ingress - HAProxy Ingress
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.
calico - Cloud native networking and network security
external-dns - Configure external DNS servers (AWS Route53, Google CloudDNS and others) for Kubernetes Ingresses and Services
oauth2-proxy - A reverse proxy that provides authentication with Google, Azure, OpenID Connect and many more identity providers.
apisix-ingress-controller - APISIX Ingress Controller for Kubernetes
k8s-helm-helmfile - Project which compares 3 approaches to deploy apps on Kubernetes cluster (using kubectl, helm & helmfile)
Caddy - Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS