ingress
ingress-nginx
ingress | ingress-nginx | |
---|---|---|
7 | 203 | |
578 | 16,718 | |
3.3% | 1.0% | |
8.3 | 9.6 | |
8 days ago | 7 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.
ingress
-
What are the most popular ingress controllers
Caddy
-
Nginx Modern Reference Architectures
That is true, unfortunately. We, the core maintainers, don't use k8s ourselves, so we need to defer to the community for help. See https://github.com/caddyserver/ingress
-
Show HN: Caddy v2.5.0
Caddy at its simplest form is an HTTP server. So you could use it to front end your application that otherwise isn't well suited for taking direct HTTP requests. Caddy would bring you other features like TLS support.
However I think in K8s world Caddy would make the most sense as an Ingress Controller. There is even a project as such: https://github.com/caddyserver/ingress
All traffic would terminate first at Caddy. Handling TLS, HTTP1/2/3, etc. Then passing it back to your application service/pod.
- Cloudflare Proxy Alternative
-
For local projects, do you change your node port range?
Sorry actually I'm mixing up caddy with traefik. And ingress is an http lb + something that talks to k8s to dynamically update the configuration. Caddy has a WIP ingress project https://github.com/caddyserver/ingress
-
Considering (and deciding against) a switch from Traefik to an Envoy-based Ingress Controller
We have an ingress controller in the works by the community here: https://github.com/caddyserver/ingress
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?
multus-cni - A CNI meta-plugin for multi-homed pods in Kubernetes
traefik - The Cloud Native Application Proxy
aws-load-balancer-controller - A Kubernetes controller for Elastic Load Balancers
emissary - open source Kubernetes-native API gateway for microservices built on the Envoy Proxy
caddy-l4 - Layer 4 (TCP/UDP) app for Caddy
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
cilium-cli - CLI to install, manage & troubleshoot Kubernetes clusters running Cilium
Caddy - Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS
haproxy-ingress - HAProxy Ingress
gateway-api - Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.
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.