https://sam-mesh.dev/docs/contributing/Recent content in Contributing on SAMHugoen-ushttps://sam-mesh.dev/docs/contributing/testnets/Mon, 01 Jan 0001 00:00:00 +0000https://sam-mesh.dev/docs/contributing/testnets/<p>The project runs two public meshes for its own testing and for anyone who wants to try the software without deploying anything.</p> <table> <thead> <tr> <th></th> <th><code>bananas.sam-mesh.dev</code></th> <th><code>hub.sam-mesh.dev</code></th> </tr> </thead> <tbody> <tr> <td>Built from</td> <td>every push to <code>main</code></td> <td>every <code>v*</code> tag</td> </tr> <tr> <td>Image tag</td> <td>the commit SHA</td> <td>the release version</td> </tr> <tr> <td>Purpose</td> <td>continuous integration of unreleased code</td> <td>the latest release, for interoperability testing</td> </tr> </tbody> </table> <p>Both are deployed by <code>.github/workflows/deploy.yaml</code> to a GKE cluster from the templates in <code>.github/k8s/</code>. Each testnet has a control plane Deployment on PostgreSQL, a router StatefulSet that announces <code>/dnsaddr/bootstrap.&lt;env&gt;.sam-mesh.dev</code> (a DNS-sync CronJob keeps the record current), the console, and a few canary nodes that publish demo services: the MCP <code>everything</code> server, an OpenRouter proxy, and a vLLM instance when one is running. Identity comes from a Dex instance at <code>auth.sam-mesh.dev</code> that accepts Google and GitHub logins, and from the cluster&rsquo;s own issuer for in-cluster workloads.</p>