From cb1391d1408a851ee7a68682062918e2b627f6d4 Mon Sep 17 00:00:00 2001 From: Romain Decker Date: Wed, 8 Feb 2023 09:25:48 +0100 Subject: [PATCH] fix: added note about sshkey support in Azure --- .../03-azure/02-create-azure-cluster.md | 10 ++++++++-- .../04-clusters/01-public-cloud/03-azure/04-aks.md | 8 +++++++- 2 files changed, 15 insertions(+), 3 deletions(-) diff --git a/content/docs/04-clusters/01-public-cloud/03-azure/02-create-azure-cluster.md b/content/docs/04-clusters/01-public-cloud/03-azure/02-create-azure-cluster.md index c60b765646..20db6f2698 100644 --- a/content/docs/04-clusters/01-public-cloud/03-azure/02-create-azure-cluster.md +++ b/content/docs/04-clusters/01-public-cloud/03-azure/02-create-azure-cluster.md @@ -84,12 +84,18 @@ If the Azure account is [registered](/clusters/public-cloud/azure/azure-cloud) w | **Resource Group** | Select the Azure resource group in which the cluster should be deployed.| | **Storage Account** | Optionally provide the storage account. Review the [Azure Storage section](/clusters/public-cloud/azure/architecture#azurestorage) for a custom storage use cases. | | **Storage Container**| Optionally provide the Azure storage container. Review the [Azure Storage section](/clusters/public-cloud/azure/architecture#azurestorage) for a custom storage use cases.| -| **SSH Key** | Public key to configure remote SSH access to the nodes.| +| **SSH Key** | Public key* to configure remote SSH access to the nodes.| | **Static Placement** | By default, Palette uses dynamic placement, in which a new VPC with a public and private subnet is created to place cluster resources for every cluster. These resources are fully managed by Palette and deleted when the corresponding cluster is deleted.
If you want to place resources into pre-existing VPCs and subnets, you can enable the **Static Placement** option. Review the [Static Placement](#static-placement-table) table below for available parameters for static placement.| |**Update worker pools in parallel**| Check the box to concurrently update the worker pools.| |**Private API Server LB**|This option applies when the cluster is deployed via the [Azure Private Endpoint](/clusters/public-cloud/azure/gateways). You can enable this option if your API Server must have private access. Review the [Private API Server LB](#private-api-server-lb-table) table below for more details.| |**Update worker pools in parallel**|If you have multiple worker pools, select the check box to enable simultaneous upgrade of all the pools. The default is sequential upgrade.| - + + + +* Azure currently supports SSH protocol 2 (SSH-2) RSA public-private key pairs with a minimum length of 2048 bits. Other key formats such as ED25519 and ECDSA are not supported. + + + #### Static Placement Table diff --git a/content/docs/04-clusters/01-public-cloud/03-azure/04-aks.md b/content/docs/04-clusters/01-public-cloud/03-azure/04-aks.md index a36280fb9a..aad50c9c12 100644 --- a/content/docs/04-clusters/01-public-cloud/03-azure/04-aks.md +++ b/content/docs/04-clusters/01-public-cloud/03-azure/04-aks.md @@ -133,7 +133,7 @@ The following steps need to be performed to provision a new cluster: | **Subscription** | Select the subscription which is to be used to access Azure Services. | | **Region** | Select a region in Azure in where the cluster should be deployed. | | **Resource Group** | Select the resource group in which the cluster should be deployed. | - | **SSH Key** | Public key to configure remote SSH access to the nodes. | + | **SSH Key** | Public key* to configure remote SSH access to the nodes. | | **Static Placement** | By default, Palette uses dynamic placement, wherein a new VPC with a public and private subnet is created to place cluster resources for every cluster. These resources are fully managed by Palette and deleted when the corresponding cluster is deleted.
Turn on the **Static Placement** option if it is desired to place resources into preexisting VPCs and subnets. If the user is making the selection of **Static Placement** of resources, the following placement information needs to be provided: ||**Virtual Resource Group**: The logical container for grouping related Azure resources. || **Virtual Network**: Select the virtual network from dropdown menu. @@ -143,6 +143,12 @@ The following steps need to be performed to provision a new cluster: +* Azure currently supports SSH protocol 2 (SSH-2) RSA public-private key pairs with a minimum length of 2048 bits. Other key formats such as ED25519 and ECDSA are not supported. + + + + + If the Palette [cloud account](/clusters/public-cloud/azure#creatinganazurecloudaccount) is created with **Disable Properties** and with **Static Placement** the network informations from user's Azure account will not be imported to palette account. Hence user can manually input the information for the ** Control Plane Subnet}>
Name
CIDR Block
Security Group Name** and the ** Worker Network}>
Name
CIDR Block
Security Group Name** (no drop down menu will be available).