You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/magnum-auto-healer/using-magnum-auto-healer.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ Like cluster-autoscaler, magnum-auto-healer is implemented to use together with
28
28
There are some considerations when we were designing the magnum-auto-healer service:
29
29
30
30
- We want to have a single component for the cluster autohealing purpose. There are already some other components out there in the community to deal with some specific tasks separately, combining them together with some customization may work, but will lead to much complexity and maintenance overhead.
31
-
- Support both master nodes and worker nodes.
31
+
- Support both control-plane nodes and worker nodes.
32
32
- Cluster administrator is able to disable the autohealing feature on the fly, which is very important for the cluster operations like upgrade or scheduled maintenance.
33
33
- The Kubernetes cluster is not necessary to be exposed to either the public or the OpenStack control plane. For example, In Magnum, the end user may create a private cluster which is not accessible even from Magnum control services.
34
34
- The health check should be pluggable. Deployers should be able to write their own health check plugin with customized health check parameters.
@@ -38,7 +38,7 @@ There are some considerations when we were designing the magnum-auto-healer serv
38
38
39
39
### Prerequisites
40
40
41
-
1. A multi-node cluster(3 masters and 3 workers) is created in Magnum.
41
+
1. A multi-node cluster(3 control-planes and 3 workers) is created in Magnum.
42
42
43
43
```
44
44
$ openstack coe cluster list
@@ -64,7 +64,7 @@ There are some considerations when we were designing the magnum-auto-healer serv
64
64
65
65
### Deploy magnum-auto-healer
66
66
67
-
It's recommended to run magnum-auto-healer service as a DaemonSet on the master nodes, the service is running in active-passive mode using leader election mechanism. There is a sample manifest file in `manifests/magnum-auto-healer/magnum-auto-healer.yaml`, you need to change some variables as needed before actually running `kubectl apply` command. The following commands are just examples:
67
+
It's recommended to run magnum-auto-healer service as a DaemonSet on the control-plane nodes, the service is running in active-passive mode using leader election mechanism. There is a sample manifest file in `manifests/magnum-auto-healer/magnum-auto-healer.yaml`, you need to change some variables as needed before actually running `kubectl apply` command. The following commands are just examples:
0 commit comments