This is an automated email from the ASF dual-hosted git repository.
dahn pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/cloudstack-documentation.git
The following commit(s) were added to refs/heads/master by this push:
new 297a011 cks: make it clear that deny acls/egress can fail pod
deployment (#174)
297a011 is described below
commit 297a011c77d39b3903af9d8d4fa4b7820300cd3e
Author: Rohit Yadav <[email protected]>
AuthorDate: Mon Jan 4 13:37:16 2021 +0530
cks: make it clear that deny acls/egress can fail pod deployment (#174)
Signed-off-by: Rohit Yadav <[email protected]>
---
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 08b71ce..4290b6c 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)
