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: cluster-autoscaler/cloudprovider/huaweicloud/README.md
+20-21Lines changed: 20 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,16 +1,16 @@
1
1
# Cluster Autoscaler on Huawei Cloud
2
2
3
3
## Overview
4
-
The cluster autoscaler for [Huawei Cloud](https://www.huaweicloud.com/) scales worker nodes within any
5
-
specified Huawei Cloud Container Engine (CCE) cluster's node pool where the `Autoscaler` label is on.
4
+
The cluster autoscaler for [Huawei ServiceStage](https://www.huaweicloud.com/intl/en-us/product/servicestage.html) scales worker nodes within any
5
+
specified container cluster's node pool where the `Autoscaler` label is on.
6
6
It runs as a Deployment on a worker node in the cluster. This README will go over some of the necessary steps required
7
7
to get the cluster autoscaler up and running.
8
8
9
9
Note:
10
10
11
-
1. Cluster autoscaler must be run on CCE v1.15.6 (Kubernetes v1.15) or later.
12
-
2. Node pool attached to the CCE cluster must have the `Autoscaler` flag turned on, and minimum number of nodes and maximum
13
-
number of nodes being set. Node pools can be managed under`Resource Management`in CCE console.
11
+
1. Cluster autoscaler must be run on a version of Huawei container engine 1.15.6 or later.
12
+
2. Node pool attached to the cluster must have the `Autoscaler` flag turned on, and minimum number of nodes and maximum
13
+
number of nodes being set. Node pools can be managed by`Resource Management`from Huawei container engine console.
14
14
3. If warnings about installing `autoscaler addon` are encountered after creating a node pool with `Autoscaler` flag on,
15
15
just ignore this warning and DO NOT install the addon.
16
16
4. Do not build your image in a Huawei Cloud ECS. Build the image in a machine that has access to the Google Container Registry (GCR).
@@ -75,7 +75,7 @@ The following steps use Huawei SoftWare Repository for Container (SWR) as an exa
75
75
```
76
76
77
77
5. For the cluster autoscaler to function normally, make sure the `Sharing Type` of the image is `Public`.
78
-
If the CCE has trouble pulling the image, go to SWR console and check whether the `Sharing Type` of the image is
78
+
If the cluster has trouble pulling the image, go to SWR console and check whether the `Sharing Type` of the image is
79
79
`Private`. If it is, click `Edit` button on top right and set the `Sharing Type` to `Public`.
80
80
81
81
### Deploy Cluster Autoscaler
@@ -111,7 +111,7 @@ and [My Credentials](https://support.huaweicloud.com/en-us/usermanual-ca/ca_01_0
111
111
112
112
- `region`
113
113
114
-
Fill in the region of the CCE here. For example, for region `Beijing4`:
114
+
Fill in the region of the cluster here. For example, for region `Beijing4`:
115
115
```
116
116
region=cn-north-4
117
117
```
@@ -122,25 +122,24 @@ and [My Credentials](https://support.huaweicloud.com/en-us/usermanual-ca/ca_01_0
122
122
123
123
#### Configure deployment
124
124
An example deployment file is provided at [examples/cluster-autoscaler-deployment.yaml](examples/cluster-autoscaler-deployment.yaml).
125
-
Change the `image` to the image you just pushed, the `cluster-name` to the CCE cluster's id and `nodes` to your
125
+
Change the `image` to the image you just pushed, the `cluster-name` to the cluster's id and `nodes` to your
126
126
own configurations of the node pool with format
127
127
```
128
128
{Minimum number of nodes}:{Maximum number of nodes}:{Node pool name}
129
129
```
130
-
The above parameters should match the parameters of the node pool you created. Currently, Huawei CCE only provides
130
+
The above parameters should match the parameters of the node pool you created. Currently, Huawei ServiceStage only provides
131
131
autoscaling against a single node pool.
132
132
133
133
More configuration options can be added to the cluster autoscaler, such as `scale-down-delay-after-add`, `scale-down-unneeded-time`, etc.
134
134
See available configuration options [here](https://github.com/kubernetes/autoscaler/blob/master/cluster-autoscaler/FAQ.md#what-are-the-parameters-to-ca).
135
135
136
-
#### Deploy cluster autoscaler on CCE
136
+
#### Deploy cluster autoscaler on the cluster
137
+
1. Log in to a machine which can manage the cluster with `kubectl`.
137
138
138
-
1. Log in to a machine which can manage the CCE cluster with `kubectl`.
139
-
140
-
Make sure the machine has kubectl access to the CCE cluster. We recommend using a worker node to manage the cluster. Follow
139
+
Make sure the machine has kubectl access to the cluster. We recommend using a worker node to manage the cluster. Follow
141
140
the instructions for
142
141
[Connecting to a Kubernetes Cluster Using kubectl](https://support.huaweicloud.com/intl/en-us/usermanual-cce/cce_01_0107.html)
143
-
to set up kubectl access to CCE cluster if you cannot execute `kubectl` on your machine.
142
+
to set up kubectl access to the cluster if you cannot execute `kubectl` on your machine.
144
143
145
144
2. Create the Service Account:
146
145
```
@@ -158,7 +157,7 @@ to set up kubectl access to CCE cluster if you cannot execute `kubectl` on your
158
157
```
159
158
160
159
### Testing
161
-
Now the cluster autoscaler should be successfully deployed on the cluster. Check it on the CCE UI console, or execute
160
+
Now the cluster autoscaler should be successfully deployed on the cluster. Check it by executing
162
161
```
163
162
kubectl get pods -n kube-system
164
163
```
@@ -212,18 +211,18 @@ and will be removed by the cluster autoscaler
212
211
213
212
## Notes
214
213
215
-
1. Huawei Cloud CCE cluster does not yet support autoscaling against multiple node pools within a single cluster, but
216
-
this is currently in development. For now, make sure that there's only one node pool with `Autoscaler` label
217
-
on in the CCE cluster.
218
-
2. If the version of the CCE cluster is v1.15.6 or older, log statements similar to the following may be present in the
214
+
1. Huawei ServiceStage does not yet support autoscaling against multiple node pools within a single cluster, but
215
+
this is currently under development. For now, make sure that there's only one node pool with `Autoscaler` label
216
+
on in the cluster.
217
+
2. If the version of the cluster is v1.15.6 or older, log statements similar to the following may be present in the
219
218
autoscaler pod logs:
220
219
```
221
220
E0402 13:25:05.472999 1 reflector.go:178] k8s.io/client-go/informers/factory.go:135: Failed to list *v1.CSINode: the server could not find the requested resource
222
221
```
223
-
This is normal and will be fixed by a future version of CCE.
222
+
This is normal and will be fixed by a future version of cluster.
224
223
225
224
## Support & Contact Info
226
225
227
226
Interested in Cluster Autoscaler on Huawei Cloud? Want to talk? Have questions, concerns or great ideas?
0 commit comments