ingress-gce
ingress
ingress-gce | ingress | |
---|---|---|
7 | 7 | |
1,253 | 574 | |
0.4% | 2.6% | |
9.0 | 8.3 | |
1 day ago | 3 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-gce
-
Server Name Indication (SNI)
You would first need to ensure you have an Ingress controller running. There are several available, such as nginx, Traefik, or the one provided by a cloud provider like GKE's Ingress-GCE or AWS's ALB Ingress Controller.
-
What are the most popular ingress controllers
ingress-gce (Google Cloud only)
-
Ingress controller confusion
Yes. Google's ingress controller talks to the GCP API and spins up an HTTP LB for you. The AWS LB Controller handles provisioning ALB's for you. And ... I guess other clouds exist too but these are the ones I am familiar with.
-
GKE Ingress: How to configure IPv4 and IPv6 addresses
At the end of the blog entry where I posted about how to fix a 502 error returned by GKE Ingress, I described an issue regarding health check configuration that has been opened for over three years. The one I mentioned here to support multiple addresses it's been opened for over four years. I think GKE Ingress is a remarkable resource. It can help you quickly release an application using K8S and cloud-native features wrapped in abstracted manifests, but it seems a bit left aside in some aspects.
-
GKE Ingress: How to fix a 502 bad gateway error
There is a considerable debate on this very topic in the issue Ingress Healthcheck Configuration on kubernetes/ingress-gce repository. Looking through issues on GitHub is an excellent way to understand how an application or service is evolving. It's been more than three years, and it's not resolved yet.
-
InterSystems Kubernetes Operator Deep Dive: Part 2
Google supports its own ingress controller, GCE, which you can use in place of an nginx controller. However, it has some drawbacks, for instance, lack of rewrite rules support, at least at the moment of writing.
-
Which ingress-controller do you use?
That ALB Controller is for AWS specifically. For Google Cloud you can use https://github.com/kubernetes/ingress-gce
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?
ingress-merge - Merge Ingress Controller for Kubernetes
multus-cni - A CNI meta-plugin for multi-homed pods in Kubernetes
ingress-nginx - Ingress-NGINX Controller for Kubernetes
aws-load-balancer-controller - A Kubernetes controller for Elastic Load Balancers
gke-managed-certs - Managed Certificates for Kubernetes clusters using GCLB
caddy-l4 - Layer 4 (TCP/UDP) app for Caddy
kubernetes-ingress-controller - :gorilla: Kong for Kubernetes: The official Ingress Controller for Kubernetes.
metallb - A network load-balancer implementation for Kubernetes using standard routing protocols
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.
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.