jedarden/zai-proxy
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
zai-proxy/notes/bf-2kl8.md

1.8 KiB
Raw Blame History

Namespace Reference Cleanup - zai-proxy.mcp → devpod

Bead: bf-2kl8 Date: 2026-07-02 Status: Complete

Summary

Removed all remaining references to zai-proxy.mcp.svc.cluster.local from the codebase and replaced them with the correct devpod namespace.

Files Modified

  1. docs/notes/CANARY_TROUBLESHOOTING_GUIDE.md

    • Line 416: zai-proxy-test.mcp.svc.cluster.local → zai-proxy-test.devpod.svc.cluster.local

  2. docs/notes/CANARY_PROMOTION_CHECKLIST.md

    • Line 43: zai-proxy-test.mcp.svc.cluster.local → zai-proxy-test.devpod.svc.cluster.local
    • Line 49: zai-proxy-test.mcp.svc.cluster.local → zai-proxy-test.devpod.svc.cluster.local
    • Line 61: zai-proxy-test.mcp.svc.cluster.local → zai-proxy-test.devpod.svc.cluster.local

  3. docs/notes/DEPLOYMENT.md

    • All service endpoint URLs updated from .mcp.svc.cluster.local to .devpod.svc.cluster.local
    • References to zai-proxy-test, zai-proxy-canary, and other services fixed

  4. docs/notes/CANARY_ROLLBACK_PROCEDURE.md

    • Line 411: zai-proxy-test.mcp.svc.cluster.local → zai-proxy-test.devpod.svc.cluster.local
    • Line 563: zai-proxy-canary.mcp.svc.cluster.local → zai-proxy-canary.devpod.svc.cluster.local

Verification

# Final verification - no remaining references in code/config/docs
grep -r "\.mcp\.svc\.cluster\.local" --include="*.go" --include="*.yaml" --include="*.md" . 2>/dev/null | grep -v "notes/bf-3ik4.md"
# Result: No matches found

Acceptance Criteria Met

  • ✅ No zai-proxy.mcp.svc.cluster.local found in any .go, .yaml, .md files
  • ✅ All replacements use the correct devpod namespace
  • ✅ Service endpoint URLs updated consistently across all documentation

Related Work

This cleanup follows the previous namespace migration work documented in notes/bf-3ik4.md.