Palette enables the provisioning of private AKS clusters within Azure Virtual networks (VNet) for enhanced security by offloading the orchestration to a Private Cloud Gateway deployed within the same account as the private AKS clusters. This private cloud gateway (Self Hosted PCGs) is an AKS cluster that needs to be launched manually and linked to an Azure cloud account in Palette Management Console. The following sections discuss the prerequisites and detailed steps towards deploying Palette self-hosted PCG for Azure Cloud Accounts. Once the self-hosted PCG is created and linked with an Azure cloud account in Palette, any Azure clusters provisioned using that cloud account will be orchestrated via the self-hosted PCG, thereby enabling the provisioning of Private AKS clusters.
- An active Azure cloud account with sufficient resource limits and permissions to provision compute, network, and security resources in the desired regions.
Create a Virtual Network in the Azure Console
- Three subnets. Each of the subnets should have a minimum of 333 available IPs. (Note: 333 IP's are required if you want to use Azure Container Networking Interface (CNI) networking and not necessary if you are using Kubenet networking)
- The VNet should have the
Microsoft.Authorization/roleAssignments/writeaction required to connect the virtual network to the Azure Kubernetes Cluster if the network configuration is
Azure CNI.for the cluster.
The VNet needs to be linked with:
- Azure Kubernetes Cluster
- Azure Bastion Host (Jump Box Virtual Machine) to connect to the Azure target Kubernetes cluster securely.
Note: A bastion host is only required if accessing a Kubernetes cluster that is located inside a private Azure Virtual Network (VNet) that only exposes private endpoints. If you have direct network access to the VNet then you do not require a bastion host. Alternatively, you can also deploy a bastion host and remove it later if no longer required.
Create an Azure Kubernetes Target Cluster in the Azure Console
- Log in to the Azure Portal and go to Kubernetes services, and click Create a Kubernetes Cluster to initiate the cluster. Creation.
- Fill up the essential information to Create Cluster Wizard and take care of the following information specifically.
- Primary Node Pool:
- Node Size: Select a VM instance with a minimum of 16 GiB RAM and four vCPUs.
- Node Count: 1 or 3 as per user requirement
- The scale method to be selected is manual.
- Networking: Two options available for networking configuration are Kubenet and Azure CNI
If this option is selected, the user needs to ensure that the VNet used is the VNet created at the previous step. This selection of VNet is not possible via Azure User Interface and hence can be achieved programmatically as below:
SUBNET_ID=$(az network vnet subnet show --resource-group resource-group-name --vnet-name vnet-name --name subnet-name --query id -o tsv)
az aks create \
--resource-group resource-group-name \
--name cluster-name \
--node-count count-value \
--network-plugin kubenet \
--vnet-subnet-id $SUBNET_ID \
- Security: For network security enable Private cluster.
In Azure CNI network configuration, select the static virtual network created from the drop-down menu.
Establish external connectivity with the Target Azure Kubernetes Cluster
To establish a connection to the Target Azure Kubernetes Cluster get connected to the Bastian Host (Jump-Box) and then get connected to the target Azure Kubernetes cluster to be imported to Palette Console as self hosted PCG.
Get Connected to Bastian Host (Jump-Box)
To establish the external connectivity for the private Kubernetes cluster, launch an Azure Virtual Machine as a jump-box with an SSH key attached.
Port Prerequisite: Add an inbound network security group rule with destination port 22.
- Open the client terminal of your choice to execute:
Ensure you have read-only access to the private key. Chmod is only supported on Linux subsystems (e.g. WSL on Windows or Terminal on Mac).
chmod 400 <keyname>.pem
Issue the command below to connect to your VM. Replace the
<private key path>with the path to your private key and
public-ip-address-of-bastion-jump-boxwith the public IP address of your VM.
ssh -i <private key path> azureuser@public-ip-address-of-bastion-jump-box
Get connected to the Target Azure Kubernetes cluster
After getting connected to the Bastion host, establish a connection to the Target Azure Kubernetes cluster. Refer to the below sample instructions:
az account set --subscription 8710ff2b-e468-434a-9a84-e522999f6b81
az aks get-credentials --resource-group resource-group-name --nametarget-cluster-name
Deploy Palette Self Hosted PCG to Palette Console
- Login to Palette console as Tenant Admin and go to Tenant settings.
- Go to Private Cloud Gateways and select + Add New Private Cloud Gateway.
From the available options, select the
Self Hosted Gateway.
In the create gateway wizard,
- Private cloud gateway name: Custom gateway name
- Cloud type: Select the cloud type as Azure for Azure self-hosted PCG.
5.Install the Palette agent (also check for prerequisites and instructions on Palette UI)
kubectl apply -f endpoint/v1/pcg/12345678901234/services/jet/manifest
kubectl apply -n cluster-1234abcd -f https://endpoint/v1/pcg/12345678901234/services/ally/manifest
The self-hosted PCG will be provisioned and will start running in the Palette console. The healthy self-hosted PCG can be managed from the Palette UI page. The healthy self-hosted PCG can be linked to Azure Cloud Account (optionally) to enjoy the enhanced security benefits. We support the PCG migration for the public cloud self-hosted PCGs as well.info
Palette users can launch Azure clusters without a PCG also. To enjoy the additional benefits of this private cloud Self-hosted PCG, users need to attach it to the Palette Azure cloud account.
Attach the Self Hosted PCG to the Azure Cloud Account
The self-hosted PCG can be attached to an existing Azure Palette cloud account or while creating a new Azure Palette cloud account. Refer to the Azure Cloud Account creation.