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: source/plugins/cloudstack-kubernetes-service.rst
+40-7Lines changed: 40 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,6 +23,8 @@ To access the Kubernetes dashboard securely, the plugin provides access to kubec
23
23
24
24
The service allows creation of Kubernetes clusters using the UI or API. Both UI and API provide the ability to list, delete, scale, upgrade, stop and start these clusters.
25
25
26
+
From ACS 4.19 onwards, you can also create `ExternalManaged` kubernetes clusters using the API. This helps provide a centralized view of kubernetes clusters managed by other providers.
27
+
26
28
Enabling the Kubernetes Service
27
29
--------------------------------
28
30
@@ -185,17 +187,19 @@ New Kubernetes clusters can be created using the API or via the UI. User will be
185
187
createKubernetesCluster API can be used to create new Kubernetes cluster. It takes following parameters as input,
186
188
187
189
- **name** (name for the Kubernetes cluster; Required)
188
-
- **description** (description for the Kubernetes cluster; Required)
190
+
- **description** (description for the Kubernetes cluster)
189
191
- **zoneid** (availability zone in which Kubernetes cluster to be launched; Required)
190
-
- **kubernetesversionid** (Kubernetes version with which cluster to be launched; Required)
191
-
- **serviceofferingid** (the ID of the service offering for the virtual machines in the cluster; Required)
192
+
- **clustertype** (Define the type of cluster: `CloudManaged` (managed by CloudStack), `ExternalManaged` (managed by an external kubernetes provider). Defaults to `CloudManaged`)
193
+
- **kubernetesversionid** (Kubernetes version with which cluster to be launched; Required for CloudManaged clusters)
194
+
- **serviceofferingid** (the ID of the service offering for the virtual machines in the cluster; Required for CloudManaged clusters)
192
195
- **account** (an optional account for the virtual machine. Must be used with domainId)
193
196
- **domainid** (an optional domainId for the virtual machine. If the account parameter is used, domainId must also be used)
194
197
- **projectid** (Deploy cluster for the project)
195
198
- **networkid** (Network in which Kubernetes cluster is to be launched)
196
199
- **keypair** (name of the ssh key pair used to login to the virtual machines)
197
-
- **controlnodes** (number of Kubernetes cluster control nodes, default is 1) externalloadbalanceripaddress (external load balancer IP address while using shared network with Kubernetes HA cluster)
198
-
- **size** (number of Kubernetes cluster worker nodes; Required)
200
+
- **controlnodes** (number of Kubernetes cluster control nodes, default is 1)
201
+
- **externalloadbalanceripaddress** (external load balancer IP address while using shared network with Kubernetes HA cluster)
202
+
- **size** (number of Kubernetes cluster worker nodes; Required for manage clusters)
199
203
- **noderootdisksize** (root disk size of root disk for each node)
200
204
- **dockerregistryusername** (username for the docker image private registry; Experimental)
201
205
- **dockerregistrypassword** (password for the docker image private registry; Experimental)
@@ -253,13 +257,19 @@ Stopping Kubernetes cluster
253
257
254
258
A running Kubernetes cluster can be stopped using either the stopKubernetesCluster API which takes id of the cluster as an input parameter or |cks-stop-action.png| action icon from UI. action icon is shown for a running cluster in the UI.
255
259
260
+
.. note::
261
+
This operation is supported only for CloudManaged kubernetes cluster.
262
+
256
263
Starting a stopped Kubernetes cluster
257
264
######################################
258
265
259
266
A stopped Kubernetes cluster can be started using either the startKubernetesCluster API which takes id of the cluster as the input parameter or the |cks-start-action.png| action icon from UI. action icon is shown for a stopped cluster in the UI.
260
267
261
268
When the service fails to start a stopped cluster, the cluster will show in Alert state else it will show up as Running.
262
269
270
+
.. note::
271
+
This operation is supported only for CloudManaged kubernetes cluster.
272
+
263
273
Scaling Kubernetes cluster
264
274
###########################
265
275
@@ -275,7 +285,9 @@ scaleKubernetesCluster API can be used to scale a running (or stopped cluster) t
275
285
276
286
Only running Kubernetes clusters can be scaled in size. When the service fails to scale the cluster, the cluster will show in Alert state else if the scaling is successfull cluster will show up in Running state.
277
287
278
-
Note: Only up scaling is supported while scaling clusters for service offering.
288
+
.. note::
289
+
- Only up scaling is supported while scaling clusters for service offering.
290
+
- This operation is supported only for CloudManaged kubernetes cluster
279
291
280
292
Upgrading Kubernetes cluster
281
293
#############################
@@ -291,7 +303,9 @@ upgradeKubernetesCluster API can be used to upgrade a running cluster. It takes
291
303
292
304
When the service fails to upgrade the cluster, the cluster will show up in Alert state, else if successful, the cluster appears Running state.
293
305
294
-
.. note:: Kubernetes can be upgraded from one MINOR version to the next MINOR version, or between PATCH versions of the same MINOR. That is, you cannot skip MINOR versions when you upgrade. For example, you can upgrade from 1.y to 1.y+1, but not from 1.y to 1.y+2. Therefore, service can upgrade running clusters in the similar manner only.
306
+
.. note::
307
+
- Kubernetes can be upgraded from one MINOR version to the next MINOR version, or between PATCH versions of the same MINOR. That is, you cannot skip MINOR versions when you upgrade. For example, you can upgrade from 1.y to 1.y+1, but not from 1.y to 1.y+2. Therefore, service can upgrade running clusters in the similar manner only.
308
+
- This operation is supported only for CloudManaged kubernetes cluster
0 commit comments