c16d7964c9
Some checks failed
CI/CD / lint (pull_request) Successful in 1m17s
CI/CD / typecheck (pull_request) Successful in 2m39s
CI/CD / test (pull_request) Successful in 1m27s
CI/CD / build (pull_request) Successful in 2m28s
CI/CD / smoke (pull_request) Failing after 3m4s
CI/CD / publish (pull_request) Has been skipped
Two corrections to the shell-bearing rebuild. **Pin by digest.** It copied from `:latest`, so a rebuild silently ships whatever upstream has moved to. When a probe started failing right after a rebuild I could not tell a version change from a broken build, and burned time on the wrong one — the binary's own `--version` prints 1.1.0 while the image label says 1.6.0, so that was a red herring too. Now pinned to sha256:dda8d56e…, which IS the running 1.6.0. **CMD, not ENTRYPOINT.** Upstream sets `Cmd: ["/app/gitea-mcp"]` with no entrypoint. mcpd maps a server's `command` to k8s `args`, which REPLACES Cmd but only APPENDS to an ENTRYPOINT — so the ENTRYPOINT form would have changed how the binary is invoked for any server that sets a command. Matching upstream's shape keeps the non-injected path byte-identical. gitea also needs `entrypoint` on its server row: its `command` is [], so there is nothing for the injector wrapper to wrap without it. Set to ["/usr/local/bin/gitea-mcp"] via apply -f (patch cannot express an array). Verified live: gitea RUNNING/healthy on secretDelivery: injector, with vault-agent-init present and the command wrapped as ["/bin/sh","-c",". /vault/secrets/gitea-creds; exec \"$0\" \"$@\"", "/usr/local/bin/gitea-mcp"] `get_me` — which needs read:user, the scope that started this whole session — returns the real account. Plaintext credentials across all mcpctl server pod specs: 4 -> 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018vybEitX4FykeMatKe5Xki