← ClaudeAtlas

vekil-reverse-proxy-deploylisted

Deploy or update Vekil from github.com/sozercan/vekil as a Kubernetes or local reverse proxy for Anthropic, Gemini, OpenAI Chat Completions, and OpenAI Responses-compatible clients. Use when the user asks to install, redeploy, configure provider routing for, expose, port-forward, validate, or troubleshoot Vekil reverse proxy deployments.
sozercan/orka · ★ 7 · AI & Automation · score 71
Install: claude install-skill sozercan/orka
# Vekil Reverse Proxy Deploy Deploy Vekil as the single reverse-proxy endpoint for Claude/Anthropic, Gemini, OpenAI-compatible, and Codex clients. Prefer the bundled Kubernetes script for repeatable cluster deployments; use Docker only for quick local runs. ## Standard Kubernetes Workflow 1. Confirm the target before changing anything: - `kubectl config current-context` - `kubectl cluster-info` - For remote/shared clusters, state the context and ask before exposing `LoadBalancer` or `NodePort` services. 2. Deploy the default zero-config Copilot-backed proxy: - `scripts/deploy_vekil_reverse_proxy.sh --context <kubectl-context>` - Default namespace: `vekil-system`; default service: `ClusterIP`; default image: `ghcr.io/sozercan/vekil:latest`; default port: `1337`. 3. If explicit provider routing is required, write or locate a JSON/YAML providers file that uses secret env references, then pass it with existing Kubernetes secrets: ```bash scripts/deploy_vekil_reverse_proxy.sh \ --context <kubectl-context> \ --providers-config /path/to/providers.yaml \ --env-secret AZURE_OPENAI_API_KEY=azure-openai:key ``` 4. For non-interactive Copilot auth in Kubernetes, either wire an existing Secret or let the script create/update one from an explicitly exported `COPILOT_GITHUB_TOKEN`. Prefer existing Secrets for production clusters that use a secret manager. ```bash # Existing Secret scripts/deploy_vekil_reverse_proxy.sh \ --env-secret CO