ingress-gce
kubernetes-ingress-controller
ingress-gce | kubernetes-ingress-controller | |
---|---|---|
7 | 8 | |
1,253 | 2,133 | |
0.4% | 0.5% | |
9.0 | 9.9 | |
1 day ago | 8 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
kubernetes-ingress-controller
- Kubernetes releases ingress2gateway tool for upcoming GA of Gateway API
- How to quickly block unwanted IP address when using ingress-nginx without the need of redeployment workloads?
-
Using Kong Ingress Controller with Spring Boot Services
Kong Ingress Controller for Kubernetes
-
Which API Gateway for K8s are you using?
Here you go! https://github.com/Kong/kubernetes-ingress-controller/issues/729
-
Full Stack Kubernetes with Kong Ingress Controller
The key to handling modern dynamic, scalable workloads in Kubernetes is a networking stack that can deliver API management, a service mesh and an ingress controller. Kong Ingress Controller allows users to manage the routing rules that control external user access to the service in a Kubernetes cluster from the same platform.
-
How I Stopped Coding Repetitive Service Components with Kong
For those organizations using Kubernetes for their container orchestration, Kong created the Kong Ingress Controller which implements authentication, transformations, and other functionalities (via plugins) across Kubernetes clusters. Kong Ingress Controller updates a standard Kubernetes implementation as shown below:
-
Using Kubernetes Ingress Controller as an API Gateway
This article will walk through how easy it is to set up the open source Kong Ingress Controller as a Kubernetes API gateway on a cluster.
-
Deployment of multiple apps on Kubernetes cluster — Walkthrough
But here is the tricky part. There are lots of Ingress Controllers available. Some of them are opensource, but some of them are paid one. For this project I’ve chosen an “official” Kubernetes Ingress Controller based on Nginx. But please be not confused with another one, also based on Nginx but created by NGINX Inc - this one is paid. Apart from these both there are also other* Ingress Controller*s available like Kong Ingress, or Traefik.
What are some alternatives?
ingress-merge - Merge Ingress Controller for Kubernetes
Kong - 🦍 The Cloud-Native API Gateway and AI Gateway.
ingress-nginx - Ingress-NGINX Controller for Kubernetes
kong-oidc-keycloak - Kong OIDC + Keycloak + httpbin
gke-managed-certs - Managed Certificates for Kubernetes clusters using GCLB
kuma - 🐻 The multi-zone service mesh for containers, Kubernetes and VMs. Built with Envoy. CNCF Sandbox Project.
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.
konga - More than just another GUI to Kong Admin API
aws-load-balancer-controller - A Kubernetes controller for Elastic Load Balancers
kanban-board - Single-click full-stack application (Postgres, Spring Boot & Angular) using Docker Compose
traefik - The Cloud Native Application Proxy