Test compilation fixes (8 integration test files): 1. Ambiguous float types — added f32/f64 annotations 2. chrono API — replaced with_hour() with date_naive().and_hms_opt() 3. Missing dev-dependencies — added sqlx + base64 4. Generic parse — wrapped f32 comparison in parens 5. Incorrect assertion — 3^5=243 > 100, changed nodes to 1000 CI fixes: 6. Missing benchmark fixtures — created 3 files in fixtures/benchmarks/ 7. clippy absurd_extreme_comparisons — usize >= 0 always true 8. authentik_jwt test — Option<SystemTime> type mismatch 9. http_server tests — removed broken RBAC test module (types deleted) Result: cargo build --all clean, cargo test --all --lib passes
This commit is contained in:
@@ -0,0 +1,33 @@
|
||||
# Kubernetes Troubleshooting Guide
|
||||
|
||||
## Port Conflicts
|
||||
|
||||
When a port conflict occurs on port 8080, check for existing services:
|
||||
|
||||
```bash
|
||||
kubectl get svc --all-namespaces | grep 8080
|
||||
```
|
||||
|
||||
### Common Causes
|
||||
|
||||
1. Multiple services binding to same NodePort
|
||||
2. Host network pods conflicting with node services
|
||||
3. Ingress controller port overlap
|
||||
|
||||
## CrashLoopBackOff
|
||||
|
||||
Pods enter CrashLoopBackOff when the container exits repeatedly.
|
||||
|
||||
### Diagnosis Steps
|
||||
|
||||
1. Check pod logs: `kubectl logs <pod> --previous`
|
||||
2. Check events: `kubectl describe pod <pod>`
|
||||
3. Check resource limits: memory/CPU constraints
|
||||
4. Check liveness probes: incorrect health check paths
|
||||
|
||||
### Resolution
|
||||
|
||||
- Increase memory limits if OOMKilled
|
||||
- Fix application startup errors
|
||||
- Adjust probe timing (initialDelaySeconds)
|
||||
- Check environment variable configuration
|
||||
Reference in New Issue
Block a user