Title: Run a second cluster beside the first on the same hosts · Issue #113 · ExaDev/github-runner · GitHub
Open Graph Title: Run a second cluster beside the first on the same hosts · Issue #113 · ExaDev/github-runner
X Title: Run a second cluster beside the first on the same hosts · Issue #113 · ExaDev/github-runner
Description: I want to run a second, independent cluster from this role on hosts that already run one, side by side, so that a cluster can be rebuilt on another mesh (a different tailnet, a new token, fresh etcd) and the runners moved to it before th...
Open Graph Description: I want to run a second, independent cluster from this role on hosts that already run one, side by side, so that a cluster can be rebuilt on another mesh (a different tailnet, a new token, fresh etc...
X Description: I want to run a second, independent cluster from this role on hosts that already run one, side by side, so that a cluster can be rebuilt on another mesh (a different tailnet, a new token, fresh etc...
Opengraph URL: https://github.com/ExaDev/github-runner/issues/113
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Run a second cluster beside the first on the same hosts","articleBody":"I want to run a second, independent cluster from this role on hosts that already run one, side by side, so that a cluster can be rebuilt on another mesh (a different tailnet, a new token, fresh etcd) and the runners moved to it before the old one is removed. Today two instances on one Docker daemon collide.\n\n`files/docker-compose.yml` names the server container `github-runner-k3s` and the agent container `github-runner-k3s-agent` literally, and publishes `6443:6443`, so a second Compose project on the same daemon fails on the container name and then on the host port. On a Colima host the port also collides on the Mac itself, since Lima forwards each VM's published ports to the host's loopback, so a second VM does not avoid it.\n\n`github_runner_cluster_container_name` only works alongside an extra Compose file that renames the container, and the agent's name has no variable at all. `github_runner_cluster_api_port` is used for the join URL every joining node dials, but k3s always listens on its default 6443 inside the container and the Compose file always publishes 6443, so setting it to anything else breaks every join.\n\nk3s writes the kubeconfig with `server: https://127.0.0.1:\u003cits listen port>`, which the role, the ARC role and anyone on the host use. So the second instance's API has to listen on its own port inside the container too, not only be published on another host port, or its kubeconfig points at the first cluster.\n\nDone when an instance with its own container names and API port runs beside one on the defaults on the same daemon, the defaults render exactly the container configuration they do today (no running server is recreated by upgrading), and the role refuses, before changing anything, an instance whose container name, host port or project directory another Compose project on that daemon already uses.\n","author":{"url":"https://github.com/Mearman","@type":"Person","name":"Mearman"},"datePublished":"2026-10-20T19:51:50Z","url":"https://github.com/ExaDev/github-runner/issues/113"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:b7cb2d50-bdee-1e90-19d4-5f5ba1324ec8 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | C710:3E338B:46C52D:611430:6B0070A6 |
| html-safe-nonce | b93f133a7d46ebc35985fc3b5fc8c2fe057acd3ad2adf72308b46549aae9f387 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJDNzEwOjNFMzM4Qjo0NkM1MkQ6NjExNDMwOjZCMDA3MEE2IiwidmlzaXRvcl9pZCI6IjcwMTI3MzMxNTU3MTUwODQ0NTUiLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | eda185c1b2cd82fc779bb344591c9f992145a1ac9412fd9bfcbaa196c4b9e4b4 |
| hovercard-subject-tag | issue:5948562036 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/ExaDev/github-runner/113/issue_layout |
| twitter:image | https://opengraph.githubassets.com/f0c530d95f7603a5cab72e5132c8538e7b72237b87787111bb760c96022a7941/ExaDev/github-runner/issues/113 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/f0c530d95f7603a5cab72e5132c8538e7b72237b87787111bb760c96022a7941/ExaDev/github-runner/issues/113 |
| og:image:alt | I want to run a second, independent cluster from this role on hosts that already run one, side by side, so that a cluster can be rebuilt on another mesh (a different tailnet, a new token, fresh etc... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | Mearman |
| hostname | github.com |
| expected-hostname | github.com |
| None | 6527e91c60c0b29d16606ff32ac5df8ecdc37a2a62205ea057a14d7762c870fa |
| turbo-cache-control | no-preview |
| go-import | github.com/ExaDev/github-runner git https://github.com/ExaDev/github-runner.git |
| octolytics-dimension-user_id | 140118018 |
| octolytics-dimension-user_login | ExaDev |
| octolytics-dimension-repository_id | 1388126104 |
| octolytics-dimension-repository_nwo | ExaDev/github-runner |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 1388126104 |
| octolytics-dimension-repository_network_root_nwo | ExaDev/github-runner |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 46f1cd2ae3cd8ae1a81019b5d619742e76f13bbd |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width