Skip to main content

Create and Manage Azure AKS Cluster

Palette supports creating and managing Azure Kubernetes Service (AKS) clusters deployed to an Azure account. This guide explains how you can create an Azure AKS cluster managed by Palette.

Prerequisites​

  • An active Azure cloud account integrated with Palette. Review Register and Manage Azure Cloud Account for guidance.

  • A Secure Shell (SSH) key that you have pre-configured in your Azure environment. Refer to the SSH Keys guide for more information about creating and managing SSH keys in Palette.

  • An infrastructure cluster profile for Azure. Review Create an Infrastructure Profile for guidance.

  • To use custom storage accounts or containers, you must create them before you create your cluster. For information about use cases for custom storage, review Azure Storage.

    tip

    If you need help creating a custom storage account or container, check out the Create a Storage Account and the Manage Blob Containers guides.

  • To enable OIDC with Microsoft Entra ID, you need to configure Entra ID with Palette. Review the Enable SSO with Microsoft Entra ID guide for more information.

  • Optionally, a Virtual Network (VNet). If you do not provide a VNet, Palette creates one for you with compute, network, and storage resources in Azure when it provisions Kubernetes clusters.

    To use a VNet that Palette creates, ensure there is sufficient capacity in your preferred Azure region to create the following resources:

    • Virtual CPU (vCPU)
    • VNet
    • Static Public IP addresses
    • Virtual Network Interfaces
    • Load Balancers
    • Virtual Hard Disk (VHD)
    • Managed Disks
    • Virtual Network Address Translation (NAT) Gateway

Deploy an Azure AKS Cluster​

  1. Log in to Palette.

  2. Ensure you are in the correct project scope.

  3. From the left Main Menu select Clusters > Add New Cluster > Deploy New Cluster.

  4. Under Cloud, select Azure and click Start Azure Configuration.

  5. Fill out the following basic information and click Next.

    FieldDescription
    Cluster NameA custom name for the cluster.
    DescriptionUse the description to provide context about the cluster.
    TagsAssign any desired cluster tags. Tags on a cluster are propagated to the Virtual Machines (VMs) deployed to the target environments. Example: region:us-west.
    Cloud AccountIf you have already added your Azure account in Palette, select it from the drop-down Menu. Otherwise, click Add New Account and add your Azure account information.

  6. Under Managed Kubernetes, select Azure AKS and select your Azure AKS cluster profile. Click Next to continue.

  7. Palette displays the cluster profile layers. Review the profile layers and customize parameters as desired in the YAML files that display when you select a layer.

    You can configure custom OpenID Connect (OIDC) for Azure clusters at the Kubernetes layer. Check out Configure OIDC Identity Provider for more information.

    warning

    All OIDC options require you to map a set of users or groups to a Kubernetes RBAC role. To learn how to map a Kubernetes role to users and groups, refer to Create Role Bindings.

  8. Click Next to continue.

  9. Configure your Azure AKS cluster using the following table for reference.

    warning

    If you enable the Disable Properties setting when registering an Azure cloud account, Palette cannot create network resources on your behalf. In this case, every time you deploy a cluster, you must manually specify its virtual network subnets and security groups.

    ParameterDescription
    SubscriptionUse the drop-down Menu to select the subscription that will be used to access Azure services.
    RegionUse the drop-down Menu to choose the Azure region where you would like to provision the cluster.
    Resource GroupSelect the name of the resource group that contains the Azure resources you will be accessing.
    Storage AccountOptionally, if you have a custom storage account available, you can use the drop-down Menu to select the storage account name. For information about use cases for custom storage, review Azure Storage.
    Storage ContainerOptionally, if you are using a custom storage container, use the drop-down Menu to select it. For information about use cases for custom storage, review Azure Storage.
    SSH KeyThe public SSH key for connecting to the nodes. SSH key pairs must be pre-configured in your Azure environment. The key you select is inserted into the provisioned VMs. For more information, review Microsoft's Supported SSH key formats.
    Enable Private ClusterWhether the control plane or API server should have internal IP addresses. Refer to the Create a private AKS cluster guide for more information.
    Static PlacementBy default, Palette uses dynamic placement. This creates a new VNet for clusters with two subnets in different Availability Zones (AZs). Palette places resources in these clusters, manages the resources, and deletes them when the corresponding cluster is deleted.

    If you want to place resources into a pre-existing VNet, enable the Static Placement option and fill out the input values listed in the Static Placement table below.

    Static Placement Settings​

    Each subnet allows you to specify the CIDR range and a security group.

    ParameterDescription
    Network Resource GroupThe logical container for grouping related Azure resources.
    Virtual NetworkSelect the VNet.
    CIDR BlockSelect the IP address CIDR range.
    Security Group NameSelect the security group name.
    Control Plane SubnetSelect the control plane subnet.
    Worker SubnetSelect the worker network.

  10. Click Next to continue.

  11. Provide the following node pool and cloud configuration information. To learn more about node pools, review the Node Pool guide.

    System Node Pool​

    To deploy an AKS cluster, you need to have at least one system node pool, which will manage the pods necessary to deploy a Kubernetes cluster, like the control plane and etcd. To add a system node pool, add a worker node pool and select the System Node Pool checkbox.

    info

    A system pool must have at least one node for development purposes. We recommend having between one and three nodes for high availability in production environments. You can configure a static node count with the Number of nodes in the pool parameter or a dynamic node count with the Enable Autoscaler parameter.

    The following table describes how to configure a system node pool.

    ParameterDescription
    Node pool nameA descriptive name for the node pool.
    Enable AutoscalerWhether Palette should scale the pool horizontally based on its per-node workload counts. If enabled, instead of the Number of nodes in the pool parameter, you will have to configure the Minimum size and Maximum size parameters, which will allow AKS to adjust the node pool size based on the workload. You can set the node count to a minimum of zero and a maximum of 1000. Setting both parameters to the same value results in a static node count.
    System Node PoolSets the pool to be a system node pool.
    Number of nodes in the poolA statically defined number of nodes in the system pool.
    Additional LabelsOptional node labels in the key-value format. To learn more, review Apply Labels to Nodes. Example: environment:production.

    System Node Pool Cloud Configuration​

    The following table describes how to configure the Azure Cloud for a system node pool.

    ParameterDescription
    Instance TypeSelect the instance type to use for all nodes in the system node pool.
    Managed diskChoose a storage option. For more information, refer to Microsoft's Storage Account Overview reference. For information about Solid State Drive (SSD) disks, refer to Standard SSD Disks for Azure Virtual Machine Workloads reference.
    Disk sizeYou can choose disk size based on your requirements. The default size is 60.

    Worker Node Pool​

    The following table describes how to configure a worker node pool.

    ParameterDescription
    Node pool nameA descriptive name for the node pool.
    Enable AutoscalerWhether Palette should scale the pool horizontally based on its per-node workload counts. If enabled, instead of the Number of nodes in the pool parameter, you will have to configure the Minimum size and Maximum size parameters, which will allow AKS to adjust the node pool size based on the workload. You can set the node count to a minimum of zero and a maximum of 1000. Setting both parameters to the same value results in a static node count.
    System Node PoolSets the pool to be a system node pool.
    Number of nodes in the poolA statically defined number of nodes in the system pool.
    Additional LabelsOptional node labels in the key-value format. To learn more, review Apply Labels to Nodes. Example: environment:production.
    TaintsYou can apply optional taint labels to a worker node pool. Review the Node Pool and Apply Taints to Nodes guides to learn more.

    Toggle the Taint button to create a taint label. When tainting is enabled, you need to provide a custom key-value pair. Use the drop-down Menu to choose one of the following Effect options:
    - NoSchedule—Pods are not scheduled onto nodes with this taint.
    - PreferNoSchedule—Kubernetes attempts to avoid scheduling pods onto nodes with this taint, but scheduling is not prohibited.
    - NoExecute—Existing pods on nodes with this taint are evicted.

    Worker Node Pool Cloud Configuration​

    The following table describes how to configure the Azure Cloud for a worker node pool.

    ParameterDescription
    Instance TypeSelect the instance type to use for all nodes in the worker node pool. You must allocate at least 2 vCPUs and 4 GB RAM across all worker nodes.
    Managed diskChoose a storage option. For more information, refer to Microsoft's Storage Account Overview reference. For information about Solid State Drive (SSD) disks, refer to Standard SSD Disks for Azure Virtual Machine Workloads reference.
    Disk sizeYou can choose disk size based on your requirements. The default size is 60.

  12. Click Next to continue.

  13. Specify your preferred OS Patching Schedule.

  14. Enable any scan options you want Palette to perform, and select a scan schedule. Palette provides support for Kubernetes configuration security, penetration testing, and conformance testing.

  15. Schedule any backups you want Palette to perform. Review Backup and Restore for more information.

  16. If you're using custom OIDC, configure the Role-Based Access Control (RBAC). You must map a set of users or groups to a Kubernetes RBAC role. To learn how to map a Kubernetes role to users and groups, refer to Create Role Bindings. Refer to Use RBAC with OIDC for an example.

  17. Click Validate and review the cluster configuration and settings summary.

  18. Click Finish Configuration to deploy the cluster. Provisioning Azure AKS clusters can take several minutes.

The cluster details page contains the status and details of the deployment. Use this page to track the deployment progress.

To learn how to remove a cluster and what to do if a force delete is necessary so you do not incur unexpected costs, refer to Cluster Removal.

Validate​

  1. Log in to Palette.

  2. Ensure you are in the correct project scope.

  3. From the left Main Menu, select Clusters. The Clusters page lists all available clusters that Palette manages.

  4. Select the Azure AKS cluster you deployed to review its details. Ensure the Cluster Status field displays the value Running.

Resources​