Skip to content

Commit 297a011

Browse files
cks: make it clear that deny acls/egress can fail pod deployment (apache#174)
Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>
1 parent 82f1660 commit 297a011

File tree

1 file changed

+3
-0
lines changed

1 file changed

+3
-0
lines changed

source/plugins/cloudstack-kubernetes-service.rst

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -137,6 +137,9 @@ The Kubernetes service provides the functionality of running and managing Kubern
137137

138138
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.
139139

140+
.. note::
141+
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.
142+
140143
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:
141144

142145
- **cloud.kubernetes.cluster.template.name.hyperv** (Name of the template to be used for creating Kubernetes cluster nodes on HyperV)

0 commit comments

Comments
 (0)