Title: Probe ServiceAccount can patch every node's key of the fleet-role-probe ConfigMap · Issue #270 · ExaDev/github-runner · GitHub
Open Graph Title: Probe ServiceAccount can patch every node's key of the fleet-role-probe ConfigMap · Issue #270 · ExaDev/github-runner
X Title: Probe ServiceAccount can patch every node's key of the fleet-role-probe ConfigMap · Issue #270 · ExaDev/github-runner
Description: Every fleet-role-probe pod runs as the same ServiceAccount, whose Role grants get and patch on the shared fleet-role-probe ConfigMap. So any node's probe token can patch any node's key: a faulty or hostile node can write a false summary ...
Open Graph Description: Every fleet-role-probe pod runs as the same ServiceAccount, whose Role grants get and patch on the shared fleet-role-probe ConfigMap. So any node's probe token can patch any node's key: a faulty or...
X Description: Every fleet-role-probe pod runs as the same ServiceAccount, whose Role grants get and patch on the shared fleet-role-probe ConfigMap. So any node's probe token can patch any node's key: a f...
Opengraph URL: https://github.com/ExaDev/github-runner/issues/270
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Probe ServiceAccount can patch every node's key of the fleet-role-probe ConfigMap","articleBody":"Every `fleet-role-probe` pod runs as the same ServiceAccount, whose Role grants `get` and `patch` on the shared `fleet-role-probe` ConfigMap. So any node's probe token can patch any node's key: a faulty or hostile node can write a false summary for another node, which the controller then judges, or enlarge the object for every node's write. The probe refuses to publish a summary over `probe_entry_limit_bytes` (#267), but that check runs in the probe and cannot bind a token used from outside it.\n\nRBAC cannot narrow this, since `resourceNames` cannot name \"the caller's node\", and a per-node Lease, Node annotation or per-node ConfigMap would each need wider grants than the current one named object.\n\nThe fix is an admission check on the ConfigMap: a ValidatingAdmissionPolicy, installed by the ARC role with the probe's other objects, that allows a probe ServiceAccount's update only when every changed data key is the node named in the request's bound token (the `authentication.kubernetes.io/node-name` extra) and the key's value is within the entry limit. It should be tested in the mesh scenarios with a write to another node's key that the API refuses.\n\nRefs #266\n","author":{"url":"https://github.com/Mearman","@type":"Person","name":"Mearman"},"datePublished":"2026-11-20T11:29:09Z","url":"https://github.com/ExaDev/github-runner/issues/270"}
| 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:84d6b5bd-363a-7561-25a1-4a7db2a13ec3 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | 9644:14591C:2EBBD5:3F3684:6B006A0B |
| html-safe-nonce | 89a4e8f504774e277b716b6b31f6bcb371db5dc0d6d0c38e5a17cc912e462d97 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiI5NjQ0OjE0NTkxQzoyRUJCRDU6M0YzNjg0OjZCMDA2QTBCIiwidmlzaXRvcl9pZCI6IjIyNjUxMjI0MzAzNzA0NzQ1MDciLCJyZWdpb25fZWRnZSI6ImlhZCIsInJlZ2lvbl9yZW5kZXIiOiJpYWQifQ== |
| visitor-hmac | bb3950b9eaf1a09b69cb02780e04a706372a2570479aedf737f6aa6070ce39a4 |
| hovercard-subject-tag | issue:6510533441 |
| 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/270/issue_layout |
| twitter:image | https://opengraph.githubassets.com/c1074df328519104ee68f065f8c0b090d2017b875c888af458f6392d5cdc9b66/ExaDev/github-runner/issues/270 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/c1074df328519104ee68f065f8c0b090d2017b875c888af458f6392d5cdc9b66/ExaDev/github-runner/issues/270 |
| og:image:alt | Every fleet-role-probe pod runs as the same ServiceAccount, whose Role grants get and patch on the shared fleet-role-probe ConfigMap. So any node's probe token can patch any node's key: a faulty or... |
| 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