docs: Remove outdated deployment files and troubleshooting content from nginx-nodeport docs

This commit is contained in:
mik-tf
2025-11-07 11:01:44 -05:00
parent 370c0d1547
commit 92688b3fec

View File

@@ -169,7 +169,6 @@ nginx → HTML
### Configuration ### Configuration
- `nginx-nodeport-deployment.yaml` - Pod configuration (starts with 1 replica, worker-friendly) - `nginx-nodeport-deployment.yaml` - Pod configuration (starts with 1 replica, worker-friendly)
- `nginx-nodeport-deployment-worker-only.yaml` - Worker-only deployment with node affinity
- `nginx-nodeport-service.yaml` - NodePort service (dual-stack) - `nginx-nodeport-service.yaml` - NodePort service (dual-stack)
- `nginx-nodeport-configmaps.yaml` - HTML content + nginx config - `nginx-nodeport-configmaps.yaml` - HTML content + nginx config
@@ -177,13 +176,9 @@ nginx → HTML
- `deploy-and-test.sh` - ⭐ **Start here** (deploy 1 worker replica + test) - `deploy-and-test.sh` - ⭐ **Start here** (deploy 1 worker replica + test)
- `update-content-many.sh` - 🚀 **For scaling** (shows all worker replica URLs) - `update-content-many.sh` - 🚀 **For scaling** (shows all worker replica URLs)
- `update-content-single.sh` - For single worker replica deployments - `update-content-single.sh` - For single worker replica deployments
- `debug-networking.sh` - 🔧 **Troubleshooting** (tests all URLs)
- `test-nodeport-ipv6.sh` - Testing and validation
### Documentation ### Documentation
- `README.md` - This guide
- `nginx-nodeport.md` - Complete technical guide - `nginx-nodeport.md` - Complete technical guide
- `TROUBLESHOOTING.md` - Common issues & solutions
--- ---
@@ -231,25 +226,9 @@ A: This makes the service accessible from all 3 worker nodes, providing global a
A: It ensures the service is only accessible on worker nodes where pods are running, preserving the source IP and improving performance. A: It ensures the service is only accessible on worker nodes where pods are running, preserving the source IP and improving performance.
**Q: How do I know if scaling worked?** **Q: How do I know if scaling worked?**
A: Use `update-content-many.sh` - it will show you all 3 accessible worker URLs. Then run `./debug-networking.sh` to confirm all are working. A: Use `update-content-many.sh` - it will show you all 3 accessible worker URLs.
--- ---
## 🆘 Getting Help
**If only 1 of 3 URLs works:**
- Run: `./debug-networking.sh` to identify which URLs work
- Check: Are all URLs actually on worker nodes (not masters)?
- Fix: Use `nginx-nodeport-deployment-worker-only.yaml` for proper worker placement
- Then: `./update-content-many.sh` and restart deployment
**Troubleshooting:**
- Check worker pod locations: `kubectl get pods -l app=nginx-nodeport -o wide`
- Test all URLs: `./debug-networking.sh`
- Verify node types: `kubectl get nodes -o wide`
- Check Mycelium status on affected worker nodes
---
## 🎉 Success! ## 🎉 Success!