Ingress-annotator

Ingress Annotator is a Kubernetes utility that dynamically applies annotation rules from a ConfigMap across Ingress resources, giving cluster and homelab…

  • Automation
  • Home Automation
  • Infrastructure
Ingress Annotator is a Kubernetes utility that dynamically applies annotation rules from a ConfigMap across Ingress resources, giving cluster and homelab operators a consistent, conflict-free way to automate Ingress configuration.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm
  • 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.

24/100 Low

Maintained
28last commit 445 days ago
Popular
165 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today

GitHub stars
5
Open issues
2
Last commit
2025-09-02
Latest release
v0.3.0
License
Apache-2.0
Activity
stale

Checked 14 days ago - source: GitHub (kuoss/ingress-annotator)

Resources & Compatibility

Requirements not published yet.

First-install notes

  • Fill in required LiveKit settings Set api_key, api_secret, ws_url, and redis in the ingress config before starting. Without them, the service can't connect to LiveKit or keep session state, so streams won't work. source
  • Open the RTMP port Open the configured RTMP TCP port (a common live-stream protocol) in your router or firewall so encoders can send live streams. If it's blocked, incoming RTMP streams simply fail to connect. source
  • Open the WHIP port for browser streams WHIP is a WebRTC way for browsers to push a stream, so also open its configured port in your firewall. If that port is blocked, browser publishers can't reach the service. source
  • Configure rules via ConfigMap Create a ConfigMap containing your reusable annotation rules, then target the namespaces or Ingress resources that should receive them; the annotator applies the annotations dynamically and keeps them consistent. source

Fetched 41 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How does Ingress Annotator manage Ingress annotations?

It uses a ConfigMap-driven approach to automate annotation management across Ingress resources.

Is it relevant for large setups where Ingress objects need repeated annotations?

The source points to using a single command or automation to apply annotations across multiple ingress objects instead of editing each object manually.

What should I check if an annotated Ingress still fails?

Check for 404 errors, TLS problems, routing failures, and ingress controller configuration issues.

Answers sourced from github.com, oneuptime.com, stackoverflow.com

Community

Collected 3 days ago - public community threads