mirror of
https://github.com/actions/actions-runner-controller.git
synced 2025-12-11 03:57:01 +00:00
docs: correct the comparison
Co-authored-by: Yusuke Kuoka <ykuoka@gmail.com>
This commit is contained in:
committed by
Yusuke Kuoka
parent
1bfd743e69
commit
7a3fa4f362
@@ -273,7 +273,7 @@ Alternatively, you can install each controller stack into a unique namespace (re
|
||||
|
||||
Runners can be deployed as 1 of 2 abstractions:
|
||||
|
||||
- A `RunnerDeployment` (based on k8s's `Deployments`)
|
||||
- A `RunnerDeployment` (similar to k8s's `Deployments`, based on `Pods`)
|
||||
- A `RunnerSet` (based on k8s's `StatefulSets`)
|
||||
|
||||
We go into details about the differences between the 2 later, initially lets look at how to deploy a basic `RunnerDeployment` at the 3 possible management hierarchies.
|
||||
|
||||
Reference in New Issue
Block a user