Topic RSS

NGINX

Saves to local browser storage. Followed topics appear on the homepage and refresh on each visit.
More context

How to proxy from one Nginx Proxy Manager to another?

Limited signal. This briefing is built from 3 sources — treat the summary as preliminary, not a comprehensive newsroom report.

Also known as nginx open source·nginx plus·nginx 1.30.1·nginx 1.31.0·ngx_http_rewrite_module

0.8 Activity score steady
Mixed Sentiment
3 Sources · 3 signals
Last updated · next ~20:00
Key Takeaway How to proxy from one Nginx Proxy Manager to another?
AI summary · grounded in cited sources
nginx open source nginx plus nginx 1.30.1 nginx 1.31.0 ngx_http_rewrite_module
Mixed 35/100
AI Brief

How to proxy from one Nginx Proxy Manager to another?

How to proxy from one Nginx Proxy Manager to another?

Recent signals

  • How to proxy from one Nginx Proxy Manager to another? r/selfhosted
  • Use-after-free in the QPACK encoder of nginx HTTP/3 - CVE-2026-42530 r/netsec
  • Nginx tuning tips: HTTPS/TLS - Turbocharge TTFB/Latency r/devops
Source-backed brief Tracked across 3 sources · brief is source backed Show all sources
r/selfhosted r/netsec r/devops

Latest from across the web

External coverage we have crawled and indexed for this topic.

View all 5 signals →
Discovery

Videos

From the channels we track

People also ask

Common questions on NGINX, surfaced from across the indexed web.

What about certificates?

We chose to use the existing certificates triggered by ingress-nginx via annotations: However, the certificates have an owner reference to the Ingress object. This means deleting an Ingress would cascade delete the Certificate and its Secret. Below one-liner, removes the ownerReference from all Certificates that reference an Ingress:

ingress-nginx to Envoy Gateway migration on CNCF internal services cluster
What Are Your Options?

With ingress-nginx entering retirement, platform teams face a choice: keep a critical control-plane component without upstream maintenance, or move to an actively supported alternative. The Kubernetes community has aligned on the Gateway API as the long-term standard for traffic management. That direction shapes your two primary migration paths: Move to another ingress controller (such as Cilium Ingress, Traefik, or HAProxy Ingress). Adopt the Kubernetes Gateway API, the next-generation standard for ingress and traffic management, using a controller like Cilium Gateway API. Cilium offers both

Navigating the ingress-nginx archival: why now is the time to move to Cilium
Which Path Should You Take First?

Most teams start with Cilium Ingress to remove the maintenance risk immediately, then move to the Gateway API as their routing and organizational needs evolve. If your platform already separates infrastructure and application teams, Gateway API will feel natural from the start. If your environment is smaller or less complex, Cilium Ingress offers the fastest path to replace ingress-nginx with minimal change. A practical migration plan: Document current behaviour: Capture hosts, paths, TLS, health checks, and any NGINX annotations. Select a target: Choose Cilium Ingress for quick replacement,

Navigating the ingress-nginx archival: why now is the time to move to Cilium
Share & embed Quotables, social share, embed snippet

Share

Embed widget

<script src="https://ttek2.com/embed/pulse/nginx" async></script>