Internal IaaS – Prerequisites

Introduction

When using the KaaS Basic (with CSE) or KaaS Standard (with Cluster API) solution on Cloud Avenue, certain technical components within your Kubernetes cluster require interaction with the vCloud Director API. These actions may include tasks such as creating disks for persistent volume , provisioning Virtual Servers (VS) on an external load balancer, or deploying Virtual Machines (VMs) when using the Cluster API…

By default, direct communication between your network within the virtual data center and the vCloud Director API is not possible.

To permit this communication, it is necessary to create a Source NAT rule within your Edge Gateway.

Source NAT Rule creation

On the vCloud Director Console go to Networking tab then clic on the Edge Gateways menu

Clic on the Edge gateway used by your Virtual Datacenter

On the left hand side menu clic on the IP Management > IP Allocations menu

Then choose an available IP address in the range 10.94.x.x allocated to your Edge Gateway.

This IP will be used in a step below.

On the left hand side menu clic on Services > NAT

Then click on New

Fill the fields like this :

Name :

VCD API Access

Interface Type :

SNAT

External IP :

The IP you choose on the precedent step

Internal IP :

CIDR of the IP range where you want to deploy your Kubernetes Nodes

Destination IP :

IP of the vCloud Director console used

(ex console2 : 195.25.13.5)

Then click on Save

Last, check your firewall rules to be sure that there is no rule that deny the communication between your network and the vCloud Director console on port 443.

---