moby-ingress
ingress
| moby-ingress | ingress | |
|---|---|---|
| 1 | 7 | |
| 7 | 574 | |
| - | 2.6% | |
| 0.0 | 8.3 | |
| about 2 years ago | 7 days ago | |
| Go | Go | |
| - | 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.
moby-ingress
-
Label-Based Docker Swarm HAProxy Ingress Controller
View on GitHub
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
What are some alternatives?
docker-swarm-ingress - Nginx swarm ingress controller, a minimalistic approach to allow routing into a Docker Swarm based on the public hostnames.
multus-cni - A CNI meta-plugin for multi-homed pods in Kubernetes
dry - dry - A Docker manager for the terminal @
aws-load-balancer-controller - A Kubernetes controller for Elastic Load Balancers
traefik-ondemand-plugin - Traefik plugin to scale containers on demand
caddy-l4 - Layer 4 (TCP/UDP) app for Caddy
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
Caddy - Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS
gateway-api - Repository for the next iteration of composite service (e.g. Ingress) and load balancing APIs.
nginx-proxy - Automated nginx proxy for Docker containers using docker-gen
kubernetes-ingress-controller - :gorilla: Kong for Kubernetes: The official Ingress Controller for Kubernetes.
kubectl-aliases - Programmatically generated handy kubectl aliases.