Skip to content

What Troupe dials

Every host this product connects to, declared by the component that connects to it. Three kinds, and the difference is what an operator needs:

  • in the source — a hostname the code has. A deployment that allows nothing else still has to allow these, and the chart's troupePolicy.allowedEgress defaults are checked against them.
  • named by a setting — somebody's own identity provider, database, bucket or key manager. The declaration is which setting names it, because the host is yours.
  • the reader's browser — fetched by a browser looking at the console, never by a pod. No NetworkPolicy governs these and an allowlist that omitted them would send somebody hunting a cluster rule for a request no pod makes.

worker

what kind why
api.anthropic.com in the source the Anthropic provider's default base URL, where a session's model calls go
api.openai.com in the source the OpenAI provider's default base URL, for a profile configured to use it
llm.endpoint (per profile) named by a setting a gateway or a self-hosted model, where a profile names one instead of a provider's own
egress.gitHosts (per profile) named by a setting the git remotes a session clones from, and the GitHub API host a profile that pushes and opens pull requests declares beside them, which the pod calls itself
mcpServers[].url (per bundle) named by a setting every MCP server a session's tools reach, named by the profile's bundle
TROUPE_OBJECT_ENDPOINT named by a setting the bucket a session's log is restored from and sealed into. The operator sets it from objectStore.endpoint
TROUPE_BAO_ADDR named by a setting the key manager: every session's key, and the per-person credentials its tools use. The operator sets it from bao.address

plane

what kind why
TROUPE_OIDC_ISSUER named by a setting the identity provider's discovery document and its signing keys
TROUPE_OIDC_TOKEN_URL named by a setting exchanging an authorization code and a device grant
DATABASE_URL named by a setting the index, the ledger and the audit trail
TROUPE_BAO_ADDR named by a setting the key manager: signing session tokens, and the per-person credential paths
the GitHub App's api_url (admin.github.put) named by a setting minting a session's installation token for the repository it clones: api.github.com unless the App is on GitHub Enterprise
object_store.endpoint named by a setting the bucket a session's log and workspace live in
notify_url (per trigger) named by a setting where a trigger posts its outcome. Absolute; not loopback, link-local, a cloud metadata address or in 100.64.0.0/10, by address or by what its name resolves to; checked at save and again at send, and posted to the address the second check passed

operator

what kind why
the cluster's API server named by a setting reconciling WorkerProfile resources, and the TokenReview a pod enrols with

console (browser)

what kind why
fonts.googleapis.com the reader's browser the console's stylesheet for IBM Plex, requested by the reader's browser
fonts.gstatic.com the reader's browser the font files themselves, requested by the reader's browser

What is not here

Anything a profile names. egress.fqdns and egress.gitHosts are a platform admin's decision per profile, checked against the policy when a bundle is published and again at admission. They are listed on the console's Integrations screen, with the cluster policy's verdict on each — which is the per-deployment answer this document cannot be.