From 4374303ec995794123a2d37b5171bfc806dbe5a7 Mon Sep 17 00:00:00 2001 From: Rohit Yadav Date: Thu, 31 Dec 2020 14:17:24 +0530 Subject: [PATCH] cks: make it clear that deny acls/egress can fail pod deployment Signed-off-by: Rohit Yadav --- source/plugins/cloudstack-kubernetes-service.rst | 3 +++ 1 file changed, 3 insertions(+) diff --git a/source/plugins/cloudstack-kubernetes-service.rst b/source/plugins/cloudstack-kubernetes-service.rst index 08b71ce71b..4290b6ce62 100644 --- a/source/plugins/cloudstack-kubernetes-service.rst +++ b/source/plugins/cloudstack-kubernetes-service.rst @@ -137,6 +137,9 @@ The Kubernetes service provides the functionality of running and managing Kubern This provides functionality to create Kubernetes clusters for Shared, Isolated and VPC networks in CloudStack, but such networks must be accessible to the CloudStack management server for provisioning virtual machines on the cluster. Template and default network offering must be set Global Settings for the service to create Kubernetes clusters. +.. note:: + In case of isolated and VPC networks, if egress rules and ACLs don't allow traffic the setup of the Kubernetes cluster and deployment of pods may fail due to inability of fetching the images from public network. + The following Global Settings value must be set to the name of Template to be used for deploying node virtual machines for the respective hypervisor while creating a Kubernetes cluster: - **cloud.kubernetes.cluster.template.name.hyperv** (Name of the template to be used for creating Kubernetes cluster nodes on HyperV)