NGINX Ingress Operator

NGINX Ingress Operator is a deprecated Kubernetes operator that helped cluster administrators deploy and manage NGINX Ingress Controller instances to route…

  • Infrastructure
  • Network Services
NGINX Ingress Operator is a deprecated Kubernetes operator that helped cluster administrators deploy and manage NGINX Ingress Controller instances to route external traffic, and its archived project was superseded by the NGINX Ingress Helm Operator.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

14/100 Low

Maintained
0GitHub repository is archived
Popular
3769 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data
Security check
08 serious findings, 6 minor, CI, tests, OpenSSF Scorecard 5.3/10

Based on 4 of 5 factors.

GitHub stars
69
Open issues
13
Last commit
2023-05-24
Latest release
v0.5.1
License
Apache-2.0
Activity
stale

Checked yesterday - source: GitHub (nginxinc/nginx-ingress-operator)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Map a host port so you can reach the site Use a port mapping like -p 8080:80 when starting the container (the first number is your host port, the second is the container port). Without it, your browser cannot reach the app even though it is running inside the container. source
  • Use a templates folder for fill-in settings Put your Nginx config template in ./templates and mount that folder to /etc/nginx/templates, then set environment variables such as MY_DOMAIN. The startup script replaces the variables with your values, so the wrong folder or missing variables can leave defaults behind. source
  • Optional: autotune worker processes Set NGINX_ENTRYPOINT_WORKER_PROCESSES_AUTOTUNE=true to make Nginx choose a worker_processes value (helper tasks that serve requests) from your CPU limit. This helps a CPU-limited container use available cores instead of a fixed or mismatched number. source
  • Deprecation This repository is deprecated; use the NGINX Ingress Helm Operator repository for new deployments. source
  • Deprecated Use the successor NGINX Ingress Helm Operator instead. source
  • Use replacement operator This operator is deprecated and archived; use nginxinc/nginx-ingress-helm-operator for new deployments. source

Fetched 4 days ago - each note links to its source

Alternatives (10)

  • Apache HTTP Server - Open-source HTTP server offering cross-platform support, modular architecture, secure configuration, robust content delivery, and extensive…
  • BunkerWeb - BunkerWeb is a self-hosted, open-source web application firewall and NGINX-based web server that protects services with secure-by-default s…
  • Caddy - Caddy is an extensible web server and reverse proxy that serves Transport Layer Security (TLS) by default, making it simple to secure and r…
  • Corvus - Self-hosted reverse proxy and web application firewall with a web console; it provides domain forwarding, free SSL, live traffic monitoring…
  • Haproxy - HAProxy is a TCP proxy and a HTTP reverse proxy.
  • Microsoft IIS - Internet Information Services (IIS) for Windows® Server is a flexible, secure and easy-to-manage Web server for hosting anything on the Web.
  • Træfik Proxy - The Cloud Native Application Proxy Simplify networking complexity while designing, deploying, and operating applications.
  • Varnish - Varnish is an open-source HyperText Transfer Protocol (HTTP) accelerator for website operators that serves cached pages from memory in fron…
  • lighttpd - Lighttpd is a secure, lightweight web server that uses memory and CPU more efficiently than comparable servers, with FastCGI, CGI, authenti…
  • nginx-ingress

Checked 40 days ago - source: AlternativeTo

Common questions

Where should I move an existing old NGINX Ingress Operator setup?

Use the NGINX Ingress Helm Operator, because the old operator repository is deprecated and will soon be archived.

Do I need a special resource before enabling TransportServers?

Yes, create a GlobalConfiguration resource before starting the Operator if you want to use TransportServers in the controller configuration.

Can I run the operator from a local machine for testing?

Yes, apply the latest CRDs to your Kubernetes/OpenShift cluster and then run make run while the operator communicates with that cluster.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads