Ingress-nginx Alternatives
Similar projects and alternatives to ingress-nginx
-
metallb
A network load-balancer implementation for Kubernetes using standard routing protocols
-
-
Scout APM
Less time debugging, more time building. Scout APM allows you to find and fix performance issues with no hassle. Now with error monitoring and external services monitoring, Scout is a developer's best friend when it comes to application development.
-
oauth2-proxy
A reverse proxy that provides authentication with Google, Azure, OpenID Connect and many more identity providers.
-
external-dns
Configure external DNS servers (AWS Route53, Google CloudDNS and others) for Kubernetes Ingresses and Services
-
emissary
open source Kubernetes-native API gateway for microservices built on the Envoy Proxy
-
-
cert-manager
Automatically provision and manage TLS certificates in Kubernetes
-
SonarQube
Static code analysis for 29 languages.. Your projects are multi-language. So is SonarQube analysis. Find Bugs, Vulnerabilities, Security Hotspots, and Code Smells so you can release quality code every time. Get started analyzing your projects today for free.
-
kubescape
Kubescape is a K8s open-source tool providing a multi-cloud K8s single pane of glass, including risk analysis, security compliance, RBAC visualizer and image vulnerabilities scanning.
-
-
-
Harbor
An open source trusted cloud native registry project that stores, signs, and scans content.
-
-
-
flannel
flannel is a network fabric for containers, designed for Kubernetes
-
-
kubernetes-ingress
NGINX and NGINX Plus Ingress Controllers for Kubernetes
-
nfs-subdir-external-provisioner
Dynamic sub-dir volume provisioner on a remote NFS server.
-
k8s-helm-helmfile
Project which compares 3 approaches to deploy apps on Kubernetes cluster (using kubectl, helm & helmfile)
-
-
ingress-nginx reviews and mentions
-
Make Testenvironments available for internal Testing
the problems seem to be already be discussed here and here but i did't solve it yet. In case somebody wants to share a nginx ingress .yml, i would welcome it :D
-
Test Out the Kubernetes Terraform Provider
The Terraform resources that have been defined so far create everything that’s needed to run an application accessible to the cluster, but more resources are needed to access the application from the outside world. Most importantly, a load balancer should be put in front of the “Hello World” service to handle the traffic. This tutorial uses the Nginx Ingress Controller and the Helm Terraform provider to create it. Add the following to main.tf to create the Nginx ingress controller:
Using the Helm Terraform provider and, in turn, the Helm chart makes creating the required Kubernetes resource much easier because it’s not necessary to add a bunch of boilerplate to the Terraform file. If you’d like to explore more than is covered in this tutorial, feel free to check out the Helm chart here. When Terraform creates the helm_release resource, it will create an ingress-nginx-controller deployment, pod, replica set, and other resources required to run the load balancer within the cluster. One more resource needs to be added to expose the Nginx controller to the outside world. Create a Kubernetes ingress for the Nginx controller by adding the following resource definition to main.tf:
-
400: Bad Request page via http/https SSL enabled k3s deployment
ingress-nginx is a community nginx ingress that's open source but uses an nginx pod. https://kubernetes.github.io/ingress-nginx/
-
A Better Way to Provision Kubernetes Resources Using Terraform
Terraform will perform the following actions: # kubernetes_namespace.nginx_ingress will be created + resource "kubernetes_namespace" "nginx_ingress" { + id = (known after apply) + metadata { + generation = (known after apply) + name = "ingress-nginx" + resource_version = (known after apply) + uid = (known after apply) } } # module.nginx_ingress.helm_release.this[0] will be created + resource "helm_release" "this" { + atomic = false + chart = "ingress-nginx" + cleanup_on_fail = false + create_namespace = false + dependency_update = false + disable_crd_hooks = false + disable_openapi_validation = false + disable_webhooks = false + force_update = true + id = (known after apply) + lint = true + manifest = (known after apply) + max_history = 0 + metadata = (known after apply) + name = "ingress-nginx" + namespace = "ingress-nginx" + recreate_pods = false + render_subchart_notes = true + replace = false + repository = "https://kubernetes.github.io/ingress-nginx" + reset_values = false + reuse_values = false + skip_crds = false + status = "deployed" + timeout = 300 + values = [] + verify = false + version = "4.1.0" + wait = false + wait_for_jobs = false + set { + name = "replicaCount" + value = "2" } } Plan: 2 to add, 0 to change, 0 to destroy.
-
Beginner Ingress Assistance Request
helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx helm template ingress-nginx ingress-nginx/ingress-nginx --namespace ingress-nginx --create-namespace --version 3.40.0 > /media/ingress-nginx_v0.50.0.yaml
You probably want to make it a DaemonSet (kind: DaemonSet in values.yaml), so that it runs a pod on all nodes (might also need a toleration if the control-plane node is tainted) and hostPort.enabled: true, so that it will listen on nodes' :80 and :443.
-
How to quickly block unwanted IP address when using ingress-nginx without the need of redeployment workloads?
You're going to have to wait for this feature: https://github.com/kubernetes/ingress-nginx/pull/7121
-
libvirt-k8s-provisioner - Ansible and terraform to build a cluster from scratch in less than 10 minutes ok KVM
nginx-ingress-controller, haproxy-ingress-controller or contour-ingress-controller for ingress management.
-
Rancher K3s: Kubernetes on Proxmox Containers
K3s ships with a Traefik ingress controller by default. This works fine, but I prefer to use the industry-standard NGINX ingress controller instead, so we'll set that up manually.
-
Deploy Kubernetes (K8s) on Amazon AWS using mixed on-demand and spot instances
You can optionally install Nginx ingress controller and Longhorn.
-
Fully automated Kubernetes (K8s) deployment on AWS using mixed on-demand and spot instances
K8s is installed through kubeadm ad uses Containerd as CRI and Flannel as CNI. You can also install longhorn for the persistent storage and nginx ingress controller for the ingress rules.
This terraform module will deploy a high available Kubernetes (K8s) cluster on Amazon AWS, using mixed on-demand and spot instances. K8s is installed through kubeadm ad usesContainerd as CRI and Flannel as CNI. You can also install longhorn for the persistent storage and nginx ingress controller for the ingress rules. Please note, this is only an example on how to Deploy a Kubernetes cluster. For a production environment you should use EKS or ECS.
-
Otomi: Self-hosted PaaS for Kubernetes on Windows (minikube)
The latest version of Otomi, by default, installs a minimal set of apps, called the Core. The core offers an advanced ingress architecture based on Istio, Nginx ingress controller, Keycloak as IdP, OAuth2 Proxy, and cert-manager. With the web UI (Otomi Console) you can add services to the mesh and securely expose them with just one click. All other integrated apps are now optional and can be activated by dragging them into the enabled apps section.
-
Setup Rancher on EKS + ALB
Rancher documentation is using nginx-ingress-controller and only creates Classic Load Balancer or Network Load Balancer. We will use AWS Load Balancer Controller to create ALB for our Rancher.
Stats
kubernetes/ingress-nginx is an open source project licensed under Apache License 2.0 which is an OSI approved license.
Popular Comparisons
Are you hiring? Post a new remote job listing for free.