configure-ingress-networking
Configures Kubernetes Ingress networking with NGINX for automated TLS management, path-based routing, and load balancing.
Install this skill
Security score
The configure-ingress-networking skill was audited on Mar 3, 2026 and we found 24 security issues across 2 threat categories. Review the findings below before installing.
Categories Tested
Security Issues
Curl to non-GitHub URL
| 98 | curl http://$INGRESS_IP |
Curl to non-GitHub URL
| 231 | curl -I http://web.example.com |
Curl to non-GitHub URL
| 235 | curl -v https://web.example.com |
Curl to non-GitHub URL
| 357 | curl https://app.example.com/ # -> web service |
Curl to non-GitHub URL
| 358 | curl https://app.example.com/api/ # -> 80% api, 20% api-v2 |
Curl to non-GitHub URL
| 359 | curl https://app.example.com/admin/ # -> admin service |
Curl to non-GitHub URL
| 360 | curl -H "X-Canary: always" https://app.example.com/api/ # -> api-v2 (100%) |
Webhook reference - potential data exfiltration
| 104 | **On failure:** For pending LoadBalancer, verify cloud provider integration and service quotas. For CrashLoopBackOff, check controller logs with `kubectl logs -n ingress-nginx -l app.kubernetes.io/com |
Webhook reference - potential data exfiltration
| 124 | --set webhook.timeoutSeconds=30 |
Webhook reference - potential data exfiltration
| 128 | kubectl get apiservice v1beta1.webhook.cert-manager.io -o yaml |
Webhook reference - potential data exfiltration
| 177 | **Expected:** cert-manager pods running in cert-manager namespace. ClusterIssuers created with Ready status. ACME account registered with Let's Encrypt. Webhook responding to certificate requests. |
Webhook reference - potential data exfiltration
| 179 | **On failure:** For webhook timeout errors, increase `webhook.timeoutSeconds` or check network policies blocking cert-manager to API server. For ACME registration failures, verify email is valid and s |
External URL reference
| 54 | helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx |
External URL reference
| 98 | curl http://$INGRESS_IP |
External URL reference
| 115 | helm repo add jetstack https://charts.jetstack.io |
External URL reference
| 138 | server: https://acme-staging-v02.api.letsencrypt.org/directory |
External URL reference
| 156 | server: https://acme-v02.api.letsencrypt.org/directory |
External URL reference
| 231 | curl -I http://web.example.com |
External URL reference
| 235 | curl -v https://web.example.com |
External URL reference
| 357 | curl https://app.example.com/ # -> web service |
External URL reference
| 358 | curl https://app.example.com/api/ # -> 80% api, 20% api-v2 |
External URL reference
| 359 | curl https://app.example.com/admin/ # -> admin service |
External URL reference
| 360 | curl -H "X-Canary: always" https://app.example.com/api/ # -> api-v2 (100%) |
External URL reference
| 422 | - **HTTP-01 challenge timeout**: Firewall blocks port 80. Let's Encrypt must reach `http://domain/.well-known/acme-challenge/` for validation. |
Install this skill with one command
/learn @pjt222/configure-ingress-networking