Nginx To Higress Migration
higress-group/higress
Migrate from ingress-nginx to Higress in Kubernetes environments.
Troubleshooting patterns for the NGINX Ingress Controller: reload failures, custom resources that have no effect, controller panics and snapshot test failures.
Install NGINX Ingress Controller Debugging
$ npx skills add nginx/kubernetes-ingress --skill nic-debugging -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install nginx/kubernetes-ingress nic-debugging --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/nginx/kubernetes-ingress.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/nic-debugging .claude/skills/nic-debugging && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "nic-debugging" agent skill from https://github.com/nginx/kubernetes-ingress/tree/main/.github/skills/nic-debugging into .claude/skills/nic-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nic-debugging", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/nginx/kubernetes-ingress/tree/main/.github/skills/nic-debuggingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add nginx/kubernetes-ingress --skill nic-debugging -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install nginx/kubernetes-ingress nic-debugging --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nginx/kubernetes-ingress.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/nic-debugging .agents/skills/nic-debugging && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "nic-debugging" agent skill from https://github.com/nginx/kubernetes-ingress/tree/main/.github/skills/nic-debugging into .agents/skills/nic-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nic-debugging", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nginx/kubernetes-ingress --skill nic-debugging -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install nginx/kubernetes-ingress nic-debugging --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nginx/kubernetes-ingress.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/nic-debugging .cursor/skills/nic-debugging && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "nic-debugging" agent skill from https://github.com/nginx/kubernetes-ingress/tree/main/.github/skills/nic-debugging into .cursor/skills/nic-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nic-debugging", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/nginx/kubernetes-ingress.git --path .github/skills/nic-debugging--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add nginx/kubernetes-ingress --skill nic-debugging -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install nginx/kubernetes-ingress nic-debugging --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nginx/kubernetes-ingress.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/nic-debugging .gemini/skills/nic-debugging && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "nic-debugging" agent skill from https://github.com/nginx/kubernetes-ingress/tree/main/.github/skills/nic-debugging into .gemini/skills/nic-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nic-debugging", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install nginx/kubernetes-ingress nic-debuggingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add nginx/kubernetes-ingress --skill nic-debugging -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/nginx/kubernetes-ingress.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/nic-debugging .github/skills/nic-debugging && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "nic-debugging" agent skill from https://github.com/nginx/kubernetes-ingress/tree/main/.github/skills/nic-debugging into .github/skills/nic-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nic-debugging", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add nginx/kubernetes-ingress --skill nic-debugging -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install nginx/kubernetes-ingress nic-debugging --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/nginx/kubernetes-ingress.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/nic-debugging .opencode/skills/nic-debugging && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "nic-debugging" agent skill from https://github.com/nginx/kubernetes-ingress/tree/main/.github/skills/nic-debugging into .opencode/skills/nic-debugging/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "nic-debugging", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
nic-debugging- GitHub stars
- 5.1k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 874 words
- Files
- 1
- Skills in repo
- 9
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Troubleshooting patterns for the NGINX Ingress Controller: reload failures, custom resources that have no effect, controller panics and snapshot test failures.
- Works in 3 steps: Check controller logs for the generated… → Look for nginx -t output in logs — shows… → Common causes
- Diagnosing an NGINX reload failure in the ingress controller
- SKILL.md covers Common Failure Modes, Log Locations, Validation and Diagnostic Tools and Debugging Workflow, plus 3 more sections
- Calls make, kubectl and git
What it does
The skill lists the most common failures in the NGINX Ingress Controller, each with a symptom, a diagnosis and a fix pattern. For a reload failure, check the controller logs for the generated config and the `nginx -t` output, which gives the exact syntax error and line. Typical causes are an unsanitized user string missing the `containsDangerousChars()` check, a template guard missing for an optional field, duplicate directives from conflicting policies and an invalid upstream when no endpoints exist. The fix is to validate earlier or repair the guard, then verify with `make test`.
A custom resource that has no effect is traced through `kubectl get vs`, its `.status.message`, controller sync errors, validation rejections, missing TLS, JWT or OIDC secrets, policies not found in the namespace and host or path conflicts. Controller panics are followed from the stack trace, usually into `internal/configs/` or `internal/k8s/`, with nil pointers on optional fields, unchecked map access and races as common causes. A snapshot test failure means template output changed, so you review the diff and either run `make test-update-snaps` or fix the template.
When your agent uses it
- Diagnosing an NGINX reload failure in the ingress controller
- Finding out why a VirtualServer or Policy resource has no effect
- Tracing a controller panic or pod restart from its logs
- Resolving snapshot test mismatches after a template change
Example prompts
- “The controller logs say reload failed; find which generated directive broke nginx -t.”
- “My VirtualServer shows state Invalid; work out why.”
- “make test fails with a snapshot mismatch after my template edit; help me decide if it is intended.”
- “Trace this controller panic back to the nil pointer in internal/configs.”
Requirements
- A checkout of the nginx/kubernetes-ingress repository
- kubectl access to the cluster running the controller
- make to run the test suite
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Check controller logs for the generated config that failed
- Look for nginx -t output in logs — shows exact syntax error and line number
- Common causes
What it can do on your machine
Read from SKILL.md and the folder at commit f6d0615. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
makekubectlgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use kubectl and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
NGINX Ingress Controller Debugging loads about 1.7k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 874 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from nginx/kubernetes-ingress at commit f6d0615, republished under its Apache-2.0 licence (© nginx). 874 words, ~1,726 tokens.
Download SKILL.mdSave it as
.claude/skills/nic-debugging/SKILL.md (or your agent's skills folder).- name
- nic-debugging
- description
- Debugging and troubleshooting patterns for NIC. Use when diagnosing failures, tracing issues, investigating NGINX reload errors, config generation bugs, or controller sync problems.
Debugging and Troubleshooting
Common Failure Modes
NGINX Reload Failure
Symptom: Controller logs show "reload failed" or NGINX returns error status.
Diagnosis:
- Check controller logs for the generated config that failed
- Look for
nginx -toutput in logs — shows exact syntax error and line number - Common causes:
- Unsanitized user string injected into config (missing
containsDangerousChars()check) - Template guard missing (
{{- if }}/{{- with }}) for optional field - Duplicate directive from conflicting policies
- Invalid upstream when no endpoints available
- Unsanitized user string injected into config (missing
Fix pattern:
- Find the template or config generation code that produced the bad directive
- Add validation to reject the input earlier, OR fix the template guard
- Verify with
make test— snapshot tests catch most template output issues
CRD Not Taking Effect
Symptom: User applies VirtualServer/Policy but NGINX config doesn't change.
Diagnosis:
- Check CRD status:
kubectl get vs <name> -o yaml— look at.status.message - Check controller logs for sync errors on that resource
- Common causes:
- Validation rejecting the resource (check
status.state: Invalid) - Missing secret reference (TLS, JWT, OIDC secrets)
- Policy referenced but not found in namespace
- Resource conflicts (duplicate host/path)
- Validation rejecting the resource (check
Controller Crash / Panic
Symptom: Pod restarts, panic in logs.
Diagnosis:
- Check logs for the panic stack trace
- Common causes:
- Nil pointer on optional CRD field (forgot
*bool/*intcheck) - Map access without nil check on
.Spec.Xfield - Race condition in concurrent secret/config access
- Nil pointer on optional CRD field (forgot
- Look for the file:line in the stack trace → usually in
internal/configs/orinternal/k8s/
Snapshot Test Failure
Symptom: make test fails with snapshot mismatch.
Diagnosis:
- This means template output changed — could be intentional or regression
- Review the diff shown in test output
- If change is intentional:
make test-update-snaps, then re-readgit diff -- '**/__snapshots__/**'to confirm only the expected directives moved - If change is unintentional: your template edit had side effects — fix the template
The inverse failure is more dangerous: you edited a .tmpl and make test-update-snaps produced no diff. That is not a pass — it means no fixture sets the field your new branch depends on. Add the fixture in template_test.go / templates_test.go and regenerate.
Log Locations
| Context | Location | What to look for |
|---|---|---|
| Controller logs | Pod stdout/stderr | Sync errors, reload status, validation failures |
| NGINX error log | /var/log/nginx/error.log in container | Config syntax errors, upstream failures |
| NGINX access log | /var/log/nginx/access.log in container | Request routing verification |
Validation and Diagnostic Tools
| Tool | Command | Purpose |
|---|---|---|
| Config test | nginx -t (inside container) | Validate NGINX config syntax |
| CRD status | kubectl get vs,vsr,ts,pol -A | Check resource state |
| Controller logs | kubectl logs <pod> -n nginx-ingress | Runtime errors |
| Describe events | kubectl describe vs <name> | Kubernetes events for the resource |
| Generated config | kubectl exec <pod> -- cat /etc/nginx/conf.d/<file> | Inspect actual generated NGINX config |
Debugging Workflow
- Reproduce — Get the exact error. Is it a reload failure? Wrong routing? Crash?
- Assess security impact — Before diving into the fix, ask:
- Is this bug exploitable? (Can external input trigger it?)
- Does the failure expose sensitive data in logs or error messages?
- Could an attacker craft input to reach this code path?
- If exploitable: flag for security review BEFORE fixing
- Locate the layer — Use logs and status to determine:
- Validation layer? →
status.state: Invalidwith reason - Config generation? → Generated config has wrong directives
- Template? → Snapshot test shows the issue
- Controller? → Sync error in logs, resource not processed
- Validation layer? →
- Isolate — Find minimum CRD/annotation that triggers the issue
- Fix — Make the change in the correct layer (don't fix templates for validation bugs)
- Verify —
make testpasses, snapshot output is correct - Prevent — Add a test case that would catch this regression (include negative/malicious input tests if the bug was in a validation path)
Show full SKILL.md (280 more words)Show less
Config Generation Debugging
When the generated NGINX config is wrong:
- Find the template struct — Which struct feeds the template? Check
internal/configs/version2/http.go(VS) orinternal/configs/version1/config.go(Ingress) - Find the config generator — Where is the struct populated? Check
internal/configs/virtualserver.goorinternal/configs/ingress.go - Find the template — Which
.tmplfile renders it? Checkinternal/configs/version2/nginx-plus.virtualserver.tmplor the OSS variant - Add a snapshot test — Create a test case in the appropriate
_test.gofile with the input that triggers the bug, runmake test-update-snapsto capture current (wrong) output, then fix and regenerate
Common Gotchas When Debugging
- NGINX config errors show line numbers in the GENERATED file, not your template — map back manually
- Secret-related failures often show as "file not found" in NGINX logs (secret not written to filesystem yet)
- Policy ordering matters — first matching policy wins, check
generatePolicies()logic - Plus-only features will work in Plus template but silently produce invalid config in OSS template
containsDangerousChars()failures are validation errors and typically result instatus.state: Invalid— check the CRD status message and controller logs
Security-Sensitive Debugging
When debugging an issue that involves user-provided input reaching NGINX config:
- Trace the input path — From CRD field / annotation → validation → config struct → template → NGINX config file. Identify every point where sanitization SHOULD happen.
- Check for injection — Can crafted input inject NGINX directives? Look for
;,{,},$, newlines, backticks in the user-controlled value. - Verify the guard — Does
containsDangerousChars()orValidateEscapedString()cover this path? If not, the bug is a security vulnerability. - Never log secrets — When debugging TLS/JWT/OIDC issues, mask credential values. Log key names and paths, not contents.
- Check RBAC — If the issue involves unauthorized access, verify ServiceAccount permissions and RBAC role bindings before looking at code.
© nginx, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .github/skills/nic-debugging of nginx/kubernetes-ingress.
Open the folder on GitHubat commit f6d0615
Compare with similar skills
NGINX Ingress Controller Debugging next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| NGINX Ingress Controller Debugging this skillnginx/kubernetes-ingress | 5.1k | — | ~1.7k | Automated safety check: Pass | Apache-2.0 | |
| Nginx To Higress Migrationhigress-group/higress | 9.5k | — | ~3.9k | Automated safety check: Pass | Apache-2.0 | |
| Intrinsic Core Debuggingintrinsic-ai/intrinsic-core | 552 | — | ~3.8k | Automated safety check: Notes | Apache-2.0 | |
| Frontend Forge Extension Operationskubesphere/kubesphere | 17k | — | ~3.2k | Automated safety check: Pass | Custom licence | |
| Tgf Server Devthkhxm/tgf | 128 | — | ~1.3k | Automated safety check: Notes | MIT | |
| Kubernetes Troubleshooting with Inspektor Gadgetinspektor-gadget/inspektor-gadget | 2.9k | — | ~2.3k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Intrinsic Core Debugging
intrinsic-ai/intrinsic-core
Meta-level debugging workflows, architectural layer isolation, and progressive disclosure routing across Envoy ingress, Kubernetes pods, Behavior Trees, ObjectWorld synchronization, ICON real-time…
Frontend Forge Extension Operations
kubesphere/kubesphere
Runs the lifecycle of FrontendExtension resources in a Kubernetes cluster: create, rebuild, package, publish, unpublish, delete and debug stuck states.
Tgf Server Dev
thkhxm/tgf
基于 tgf v2（github.com/thkhxm/tgf/v2）用确定性的 tgfctl 工作流创建、验证和维护 Go 游戏服务器项目。
Kubernetes Troubleshooting with Inspektor Gadget
inspektor-gadget/inspektor-gadget
Traces what the kernel is doing for a misbehaving pod using Inspektor Gadget's eBPF tools, tagged with namespace, pod, container and node, without changing workloads.
Frontend Forge FI Operations
kubesphere/kubesphere
Operates FrontendIntegration resources and the frontend-forge extension with kubectl: create from YAML, update, enable, disable, delete, inspect and troubleshoot builds.
More from nginx/kubernetes-ingress
All 9 skills in this repoNGINX Ingress Controller Feature Checklists
nginx/kubernetes-ingress
Gives step-by-step checklists for adding Ingress annotations, VirtualServer fields and Helm values to the NGINX Kubernetes Ingress Controller, with common gotchas.
NGINX Ingress Policy CRD Guide
nginx/kubernetes-ingress
Step-by-step checklist for adding a new Policy CRD type to the NGINX Ingress Controller, from the Go types and validation to config generation and templates.
NGINX Ingress CI Pipelines
nginx/kubernetes-ingress
Explains how the NGINX Ingress Controller's GitHub Actions workflows, reusable workflows, build matrices and release pipeline fit together across two repositories.
NGINX Ingress Controller Image Builder
nginx/kubernetes-ingress
Explains the multi-stage Dockerfile, the 25 image variant combinations, and the Makefile targets for building NGINX Ingress Controller images.
NGINX Ingress Controller Structure
nginx/kubernetes-ingress
Maps the NGINX Kubernetes Ingress Controller codebase: repository layout, architectural layers, layer-crossing rules and which files are generated.
NIC Testing Patterns
nginx/kubernetes-ingress
Testing conventions for the NGINX Ingress Controller repo: Go table-driven tests, mandatory snapshot regeneration, Helm tests and Python pytest integration tests.
Related
Works with
Categories
Questions about NGINX Ingress Controller Debugging
What does NGINX Ingress Controller Debugging do?
Troubleshooting patterns for the NGINX Ingress Controller: reload failures, custom resources that have no effect, controller panics and snapshot test failures. The skill lists the most common failures in the NGINX Ingress Controller, each with a symptom, a diagnosis and a fix pattern. For a reload failure, check the controller logs for the generated config and the `nginx -t` output, which gives the exact syntax error and line.
When should I use NGINX Ingress Controller Debugging?
NGINX Ingress Controller Debugging fits situations like: diagnosing an NGINX reload failure in the ingress controller; finding out why a VirtualServer or Policy resource has no effect; tracing a controller panic or pod restart from its logs; resolving snapshot test mismatches after a template change.
How do I install NGINX Ingress Controller Debugging in Claude Code?
Run `npx skills add nginx/kubernetes-ingress --skill nic-debugging -a claude-code`. Or copy the skill folder (.github/skills/nic-debugging in nginx/kubernetes-ingress) into .claude/skills/nic-debugging in your project. Claude Code loads it when a task matches its description.
How do I install NGINX Ingress Controller Debugging in Codex?
Run `npx skills add nginx/kubernetes-ingress --skill nic-debugging -a codex`. Or copy the skill folder (.github/skills/nic-debugging in nginx/kubernetes-ingress) into .agents/skills/nic-debugging in your project. Codex loads it when a task matches its description.
Can I use NGINX Ingress Controller Debugging in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add nginx/kubernetes-ingress --skill nic-debugging -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/nic-debugging, .gemini/skills/nic-debugging, .github/skills/nic-debugging and .opencode/skills/nic-debugging in your project.
What does NGINX Ingress Controller Debugging need to run?
Going by SKILL.md and its folder, NGINX Ingress Controller Debugging needs the command-line tools its instructions call (make, kubectl and git). Our summary lists: A checkout of the nginx/kubernetes-ingress repository; kubectl access to the cluster running the controller; make to run the test suite.
Does NGINX Ingress Controller Debugging access the network?
SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is NGINX Ingress Controller Debugging safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does NGINX Ingress Controller Debugging use?
NGINX Ingress Controller Debugging is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does NGINX Ingress Controller Debugging use?
About 1.7k tokens (SKILL.md is roughly 6.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to NGINX Ingress Controller Debugging?
Skills that share tags, products or a category with NGINX Ingress Controller Debugging: Nginx To Higress Migration (higress-group/higress, 9.5k stars), Intrinsic Core Debugging (intrinsic-ai/intrinsic-core, 552 stars), Frontend Forge Extension Operations (kubesphere/kubesphere, 17k stars) and Tgf Server Dev (thkhxm/tgf, 128 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains NGINX Ingress Controller Debugging?
nginx (a GitHub organization) maintains it in nginx/kubernetes-ingress, which has 5,082 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 7, 2026.
Source: nginx/kubernetes-ingress on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.