feat(repo-cache): add approved private repository allowlist - #208
Merged
Conversation
Extend the repo-cache-sync Deployment with two credentialed git-sync v4.7.1 containers, sync-agent-knowledge (probe 9831) and sync-channel-project (probe 9832), cloning the only two private, non-archived makeitworkcloud repositories (verified 2026-09-05, both default branch main) at HEAD, depth 1, 120s period, max-failures -1, group-write, into the existing mcp-repo-cache PVC behind the unchanged read-only repo-search backend. Authentication uses git-sync v4's documented --username=x-access-token and --password-file=/etc/git-secret/github_token; the existing SOPS-encrypted Secret mcp-makeitwork-github-token is mounted read-only at /etc/git-secret in those two containers only. The encrypted Secret source was never decrypted, read, or modified. The Kustomize inline resource-null patch lists both new containers so the single-node no-resources policy stays consistent. Comments and docs that called the cache public-only or excluded agent-knowledge/channel-project now distinguish the public-only automatic discovery design from this explicit owner-approved private allowlist. The repo-search tool filter and external exposure are unchanged, and this branch push opens no pull request, merges nothing, dispatches no workflow, and syncs or deploys nothing.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds the owner-approved
agent-knowledgeandchannel-projectrepositories to the internal, read-only repository cache. Each uses a credentialedgit-syncv4.7.1 container, while public automatic discovery remains credential-free and public-only.Fixes #
None — owner-approved repository-cache access change.
Type of change
Validation
testrun 33945440569 passed.No local Kubernetes, Kustomize, SOPS, OpenTofu, or live-system operation was run or claimed. CI is the validation authority.
Impact and rollout
Producer: the existing
mcp-makeitwork-github-tokenSecret is the only credential reference. Its encrypted source is unchanged. GitHub currently reports exactly two private, non-archived organization repositories:agent-knowledgeandchannel-project, both withmainas their default branch.Consumer: the existing
repo-cache-syncDeployment writes the two cache roots to the existingmcp-repo-cachePVC; the unchanged internalrepo-searchMCP backend continues to mount that PVC read-only. The MCP tool filter, endpoint exposure, OpenCode chart, public automatic discovery, and all public cache sources are unchanged.Delivery stages: this PR authors GitOps desired state only. After an explicitly approved merge,
mainCI must pass and the sync workflow may submit the tested revision to Argo CD. Verify themcp-gatewayApplication, the two new git-sync containers,/repos/{agent-knowledge,channel-project}/current, and the internal repo-search response separately. Nothing here proves reconciliation, health, or functional cache reads.Rollback: remove the owner-approved private allowlist through a reviewed GitOps PR. Do not patch the Deployment or PVC live.
Safety and secrets
GitHub Advanced Security secret scanning is unavailable for this repository; the diff was manually inspected. AI-assisted change: an OpenCode agent materially produced this change; reviewers should verify the approved private-repository scope, read-only Secret mount, and preserved public-only discovery boundary before merging.