From d7129735ee139bfeb898eb1097407c8e392c2348 Mon Sep 17 00:00:00 2001 From: Abhishek Kumar Date: Fri, 7 Feb 2025 17:28:21 +0530 Subject: [PATCH 1/2] cks: update docs for removed createKubernetesCluster API param dockerregistryemail has been removed in https://github.com/apache/cloudstack/commit/e0a5df50ceb3293c0875b7c2e8961d4e666a0e92 Signed-off-by: Abhishek Kumar --- source/plugins/cloudstack-kubernetes-service.rst | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/source/plugins/cloudstack-kubernetes-service.rst b/source/plugins/cloudstack-kubernetes-service.rst index 70f394d515..26a5666049 100644 --- a/source/plugins/cloudstack-kubernetes-service.rst +++ b/source/plugins/cloudstack-kubernetes-service.rst @@ -214,7 +214,6 @@ createKubernetesCluster API can be used to create new Kubernetes cluster. It tak - **dockerregistryusername** (username for the docker image private registry; Experimental) - **dockerregistrypassword** (password for the docker image private registry; Experimental) - **dockerregistryurl** (URL for the docker image private registry; Experimental) -- **dockerregistryemail** (email of the docker image private registry user; Experimental) For example: @@ -253,7 +252,7 @@ On successful creation, the new cluster will automatically be started and will s .. note:: - A minimum of 2 cores of CPU and 2GB of RAM is needed for deployment. Therefore, the serviceofferingid parameter of createKubernetesCluster API must be provided with the ID of such compute offerings that conform to these requirements. - - Private docker registry related parameters of createKubenetesCluster API (dockerregistryusername, dockerregistryusername, dockerregistryurl, dockerregistryemail) provides experimental functionality. To use them during cluster deployment value for global setting, cloud.kubernetes.cluster.experimental.features.enabled, must be set to true by admin beforehand. + - Private docker registry related parameters of createKubenetesCluster API (dockerregistryusername, dockerregistryusername, dockerregistryurl) provides experimental functionality. To use them during cluster deployment value for global setting, cloud.kubernetes.cluster.experimental.features.enabled, must be set to true by admin beforehand. Listing Kubernetes clusters ############################ From c34de01206dc44840855487b8f7b600c392a91df Mon Sep 17 00:00:00 2001 From: Abhishek Kumar Date: Sat, 8 Feb 2025 00:25:02 +0530 Subject: [PATCH 2/2] Update source/plugins/cloudstack-kubernetes-service.rst --- source/plugins/cloudstack-kubernetes-service.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/plugins/cloudstack-kubernetes-service.rst b/source/plugins/cloudstack-kubernetes-service.rst index 26a5666049..d8f59ed558 100644 --- a/source/plugins/cloudstack-kubernetes-service.rst +++ b/source/plugins/cloudstack-kubernetes-service.rst @@ -252,7 +252,7 @@ On successful creation, the new cluster will automatically be started and will s .. note:: - A minimum of 2 cores of CPU and 2GB of RAM is needed for deployment. Therefore, the serviceofferingid parameter of createKubernetesCluster API must be provided with the ID of such compute offerings that conform to these requirements. - - Private docker registry related parameters of createKubenetesCluster API (dockerregistryusername, dockerregistryusername, dockerregistryurl) provides experimental functionality. To use them during cluster deployment value for global setting, cloud.kubernetes.cluster.experimental.features.enabled, must be set to true by admin beforehand. + - Private docker registry related parameters of createKubenetesCluster API (dockerregistryusername, dockerregistrypassword, dockerregistryurl) provides experimental functionality. To use them during cluster deployment value for global setting, cloud.kubernetes.cluster.experimental.features.enabled, must be set to true by admin beforehand. Listing Kubernetes clusters ############################