Project Name | Stars | Downloads | Repos Using This | Packages Using This | Most Recent Commit | Total Releases | Latest Release | Open Issues | License | Language |
---|---|---|---|---|---|---|---|---|---|---|
Kong | 35,973 | 9 hours ago | 233 | apache-2.0 | Lua | |||||
🦍 The Cloud-Native API Gateway | ||||||||||
Kuboard Press | 19,085 | a month ago | 365 | JavaScript | ||||||
Kuboard 是基于 Kubernetes 的微服务管理界面。同时提供 Kubernetes 免费中文教程,入门教程,最新版本的 Kubernetes v1.23.4 安装手册,(k8s install) 在线答疑,持续更新。 | ||||||||||
Authelia | 17,456 | 2 | 5 hours ago | 64 | October 28, 2019 | 98 | apache-2.0 | Go | ||
The Single Sign-On Multi-Factor portal for web apps | ||||||||||
Ingress Nginx | 15,613 | 1 | 14 hours ago | 63 | July 21, 2021 | 534 | apache-2.0 | Go | ||
Ingress-NGINX Controller for Kubernetes | ||||||||||
External Dns | 6,702 | 9 | 13 hours ago | 137 | May 24, 2023 | 241 | apache-2.0 | Go | ||
Configure external DNS servers (AWS Route53, Google CloudDNS and others) for Kubernetes Ingresses and Services | ||||||||||
K8s For Docker Desktop | 4,707 | 3 months ago | 43 | apache-2.0 | PowerShell | |||||
为Docker Desktop for Mac/Windows开启Kubernetes和Istio。 | ||||||||||
Flagger | 4,428 | 7 | 3 days ago | 59 | July 14, 2023 | 239 | apache-2.0 | Go | ||
Progressive delivery Kubernetes operator (Canary, A/B Testing and Blue/Green deployments) | ||||||||||
Kubernetes Ingress | 4,368 | 3 | 21 hours ago | 102 | October 19, 2022 | 82 | apache-2.0 | Go | ||
NGINX and NGINX Plus Ingress Controllers for Kubernetes | ||||||||||
Aws Load Balancer Controller | 3,536 | 19 hours ago | 18 | June 28, 2021 | 192 | apache-2.0 | Go | |||
A Kubernetes controller for Elastic Load Balancers | ||||||||||
Contour | 3,507 | 37 | a day ago | 169 | July 28, 2023 | 355 | apache-2.0 | Go | ||
Contour is a Kubernetes ingress controller using Envoy proxy. |
This repository contains the OpenShift routers for NGINX, HAProxy, and F5. They read Route
objects out of the
OpenShift API and allow ingress to services. HAProxy is currently the reference implementation. See the details
in each router image.
These images are managed by the cluster-ingress-operator
in an OpenShift 4.0+ cluster.
The template router code (openshift-router
) is generic and creates config files on disk based on the state
of the cluster. The process launches proxies as children and triggers reloads as necessary after new config
has been written. The standard logic for handling conflicting routes, supporting wildcards, reporting status
back to the Route object, and metrics live in the standard process.
The OpenShift router can be run against a vanilla Kubernetes cluster, although some of the security protections present in the API are not possible with CRDs.
To deploy, clone this repository and then run:
$ kubectl create -f deploy/
You will then be able to create a Route
that points to a service on your cluster and the router pod will
forward your traffic from port 80 to your service endpoints. You can run the example like:
$ kubectl create -f example/
And access the router via the node it is located on. If you're running locally on minikube or another solution, just run:
$ curl http://localhost -H "Host: example.local"
to see your route and:
$ kubectl get routes
to see details of your routes.