rock
b15072e12d
CI / CI (push) Successful in 11m36s
## Problem 8 integration test files failed to compile due to: 1. Ambiguous float types (Rust 2024+ stricter inference) 2. chrono 0.4 API change (`with_hour` removed) 3. Missing `sqlx` + `base64` in `[dev-dependencies]` 4. `<` parsed as generics instead of comparison 5. Incorrect assertion (3^5=243 > 100) ## Fix - Added `f32`/`f64` type annotations to vec declarations and bindings - Replaced `with_hour(0)` with `date_naive().and_hms_opt(0,0,0).unwrap().and_utc()` - Added `sqlx` + `base64` to `[dev-dependencies]` - Wrapped comparison in parens - Fixed assertion: nodes=100 → nodes=1000 ## Validation - `cargo build --release` clean - `cargo test` — 20 test suites, 0 failures - 10 files changed, 46 insertions, 42 deletionsReviewed-on: #46 Co-authored-by: rock <[email protected]>
34 lines
822 B
Plaintext
34 lines
822 B
Plaintext
# 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
|