Azure support for Dedicated (#33)

* #2669 Azure support for Dedicated * minor edit * update regions, per Nate * minor edit in nav.adoc * remove Norway East + nav edits * note only support tiers 1-3 * rename file and add redirect renamed so the page doens't look specific to AWS * Add automation for npm update (#35) * Add GH Action * Update reviewers * Apply suggestions from code review * Update update-extensions.yml * Update update-extensions.yml (#37) * Update @redpanda-data/docs-extensions-and-macros (#42) Co-authored-by: vbotbuildovich <[email protected]> * Use 'jq -r' instead of sed to remove quotes (#40) * Add Azure to cloud docs (#38) * Add Dedicated to Private Link doc * Add Azure to Cloud API docs * Minor edit to code examples * Add Private Link to nav tree under Dedicated * Note that the page is for AWS steps only * Tabs in alphabetical order * update rpk cloud byoc (#39) * #2226 update rpk cloud byoc * minor nav update * change what's new from August to Sept * minor edits from doc review --------- Co-authored-by: Jake Cahill <[email protected]> Co-authored-by: vbotbuildovich <[email protected]> Co-authored-by: vbotbuildovich <[email protected]> Co-authored-by: Michael Maltese <[email protected]> Co-authored-by: Kat Batuigas <[email protected]>
redpanda-data · Sep 4, 2024 · 65d3e5c · 65d3e5c
1 parent 5cc1737
commit 65d3e5c
Show file tree

Hide file tree

Showing 8 changed files with 39 additions and 22 deletions.
diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc
@@ -4,17 +4,18 @@
 ** xref:get-started:cloud-overview.adoc[Introduction to Redpanda Cloud]
 *** xref:get-started:intro-to-events.adoc[]
 *** xref:get-started:architecture.adoc[]
-** xref:get-started:cluster-types/index.adoc[Cluster Types]
-*** xref:get-started:cluster-types/serverless.adoc[Serverless]
-*** xref:get-started:cluster-types/byoc/index.adoc[BYOC]
-**** xref:get-started:cluster-types/byoc/create-byoc-cluster-aws.adoc[]
-**** xref:get-started:cluster-types/byoc/create-byoc-cluster-azure.adoc[]
-**** xref:get-started:cluster-types/byoc/create-byoc-cluster-gcp.adoc[]
-**** xref:get-started:cluster-types/byoc/vpc-byo-gcp.adoc[]
-**** xref:get-started:cluster-types/byoc/remote-read-replicas.adoc[Create a Remote Read Replica Topic]
-*** xref:get-started:cluster-types/dedicated/index.adoc[Dedicated]
-**** xref:get-started:cluster-types/dedicated/quick-start-cloud.adoc[Dedicated Cluster Quickstart]
-**** xref:get-started:cluster-types/dedicated/create-dedicated-cloud-cluster-aws.adoc[]
+
+* xref:get-started:cluster-types/index.adoc[Deploy]
+** xref:get-started:cluster-types/serverless.adoc[Serverless]
+** xref:get-started:cluster-types/byoc/index.adoc[BYOC]
+*** xref:get-started:cluster-types/byoc/create-byoc-cluster-aws.adoc[]
+*** xref:get-started:cluster-types/byoc/create-byoc-cluster-azure.adoc[]
+*** xref:get-started:cluster-types/byoc/create-byoc-cluster-gcp.adoc[]
+*** xref:get-started:cluster-types/byoc/vpc-byo-gcp.adoc[]
+*** xref:get-started:cluster-types/byoc/remote-read-replicas.adoc[Create a Remote Read Replica Topic]
+** xref:get-started:cluster-types/dedicated/index.adoc[Dedicated]
+*** xref:get-started:cluster-types/dedicated/quick-start-cloud.adoc[Dedicated Cluster Quickstart]
+*** xref:get-started:cluster-types/dedicated/create-dedicated-cloud-cluster.adoc[]
 ** xref:get-started:create-topic.adoc[Create a Topic]
 ** xref:get-started:config-topics.adoc[Manage Topics]
 

diff --git a/modules/get-started/pages/cloud-overview.adoc b/modules/get-started/pages/cloud-overview.adoc
@@ -21,8 +21,6 @@ NOTE: With standard BYOC clusters, Redpanda manages security policies and resour
 
 With Serverless clusters, you host your data in Redpanda's VPC, and Redpanda handles automatic scaling, provisioning, operations, and maintenance. This is a production-ready deployment option with a cluster available instantly. There is no base cost, and with pay-as-you-go billing after the free trial, you only pay for what you consume. You can view detailed billing activity for each cluster and edit payment methods on the *Billing* page. 
 
-Available on AWS.
-
 ==== Sign up for Serverless
 
 To start using Serverless, https://redpanda.com/try-redpanda/cloud-trial#serverless[sign up for a free trial^]. New trials receive $100 (USD) in free credits to spend in the first 14 days. This should be enough to run Redpanda with reasonable throughput. No credit card is required for a trial. To continue using your Serverless cluster after the free trial, add a credit card and pay as you go. 
@@ -31,7 +29,7 @@ NOTE: Serverless is currently in a limited availability (LA) release with xref:g
 
 === Dedicated Cloud
 
-With Dedicated clusters, you host your data on Redpanda cloud resources (AWS or GCP), and Redpanda handles provisioning, operations, and maintenance. Dedicated clusters are single-tenant deployments that support private networking (that is, VPC peering to talk over private IPs) for better data isolation.
+With Dedicated clusters, you host your data on Redpanda cloud resources (AWS, GCP, or Azure), and Redpanda handles provisioning, operations, and maintenance. Dedicated clusters are single-tenant deployments that support private networking (for example, VPC peering to talk over private IPs) for better data isolation.
 When you create a Dedicated cluster, you select the supported xref:reference:tiers/dedicated-tiers.adoc[tier] that meets your compute and storage needs. 
 
 ==== Sign up for Dedicated
@@ -62,7 +60,7 @@ With Serverless (or if you sign up for Dedicated through the AWS Marketplace), y
 Dedicated and BYOC clusters offer the following features:
 
 * Single-zone or multi-zone availability (a multi-zone cluster provides higher resiliency in the event of a failure in one of the zones)
-* Private networking using VPC peering
+* Private networking using VPC peering or a private connectivity service, such as AWS PrivateLink, GCP Private Service Connect, or Azure Private Link. 
 * Ability to export metrics to a 3rd-party monitoring system
 * Managed connectors
 * Higher limits and quotas (see xref:get-started:cluster-types/serverless.adoc#limits[Serverless limits])

diff --git a/modules/get-started/pages/cluster-types/byoc/create-byoc-cluster-aws.adoc b/modules/get-started/pages/cluster-types/byoc/create-byoc-cluster-aws.adoc
@@ -10,7 +10,7 @@ See also: xref:get-started:cloud-overview.adoc#redpanda-cloud-architecture[Redpa
 
 . Log in to https://cloud.redpanda.com[Redpanda Cloud^].
 . On the Clusters page, click *Create cluster*, then click *Create BYOC cluster*. 
-. Enter a cluster name, then select the resource group, provider (AWS), xref:reference:tiers/byoc-tiers.adoc[region, tier], availability zones, and Redpanda version.
+. Enter a cluster name, then select the resource group, provider (AWS), xref:reference:tiers/byoc-tiers.adoc[region, tier], availability, and Redpanda version.
 +
 [NOTE]
 ==== 

diff --git a/modules/get-started/pages/cluster-types/byoc/create-byoc-cluster-azure.adoc b/modules/get-started/pages/cluster-types/byoc/create-byoc-cluster-azure.adoc
@@ -64,7 +64,7 @@ See also: xref:get-started:cloud-overview.adoc#redpanda-cloud-architecture[Redpa
 
 . Log in to https://cloud.redpanda.com[Redpanda Cloud^].
 . On the Clusters page, click *Create cluster*, then click *Create BYOC cluster*.
-. Enter a cluster name, then select the resource group, provider (Azure), xref:reference:tiers/byoc-tiers.adoc[region, tier], availability zones, and Redpanda version. 
+. Enter a cluster name, then select the resource group, provider (Azure), xref:reference:tiers/byoc-tiers.adoc[region, tier], availability, and Redpanda version. 
 +
 [NOTE]
 ==== 

diff --git a/modules/get-started/pages/cluster-types/byoc/create-byoc-cluster-gcp.adoc b/modules/get-started/pages/cluster-types/byoc/create-byoc-cluster-gcp.adoc
@@ -13,7 +13,7 @@ See also: xref:get-started:cloud-overview.adoc#redpanda-cloud-architecture[Redpa
 . Log in to https://cloud.redpanda.com[Redpanda Cloud^].
 . On the Clusters page, click *Create cluster*, then click *Create BYOC cluster*.
 +
-Enter a cluster name, then select the resource group, provider (GCP), xref:reference:tiers/byoc-tiers.adoc[region, tier], availability zones, and Redpanda version.
+Enter a cluster name, then select the resource group, provider (GCP), xref:reference:tiers/byoc-tiers.adoc[region, tier], availability, and Redpanda version.
 +
 [NOTE]
 ====

diff --git a/...d/create-dedicated-cloud-cluster-aws.adoc → ...cated/create-dedicated-cloud-cluster.adoc b/...d/create-dedicated-cloud-cluster-aws.adoc → ...cated/create-dedicated-cloud-cluster.adoc
@@ -1,14 +1,14 @@
 = Create a Dedicated Cloud Cluster
 :description: Learn how to create a Dedicated cluster.
-:page-aliases: cloud:create-dedicated-cloud-cluster-aws.adoc, deploy:deployment-option/cloud/provision-a-dedicated-cluster/index.adoc, deploy:deployment-option/cloud/create-dedicated-cloud-cluster-aws.adoc
+:page-aliases: cloud:create-dedicated-cloud-cluster-aws.adoc, deploy:deployment-option/cloud/provision-a-dedicated-cluster/index.adoc, deploy:deployment-option/cloud/create-dedicated-cloud-cluster-aws.adoc, get-started:cluster-types/dedicated/create-dedicated-cloud-cluster-aws.adoc
 
 After you log in to https://cloud.redpanda.com[Redpanda Cloud^], you land on the *Clusters* page. This page lists all the clusters in your organization. 
 
 == Create a Dedicated cluster
 
 . On the Clusters page, click *Create cluster*, then click *Create Dedicated cluster*.
 +
-Enter a cluster name, then select the resource group, cloud provider (AWS or GCP), xref:reference:tiers/dedicated-tiers.adoc[region, availability zones, tier], and Redpanda version.
+Enter a cluster name, then select the resource group, cloud provider (AWS, GCP, or Azure), xref:reference:tiers/dedicated-tiers.adoc[region, tier], availability, and Redpanda version.
 +
 [NOTE]
 ====
@@ -21,7 +21,7 @@ Enter a cluster name, then select the resource group, cloud provider (AWS or GCP
 ** Your network name is used to identify this network.
 ** For a xref:networking:cidr-ranges.adoc[CIDR range], choose one that does not overlap with your existing VPCs or your Redpanda network.
 +
-NOTE: Private networks require either a VPC peering connection or a private connectivity service, such as AWS PrivateLink or GCP Private Service Connect. 
+NOTE: Private networks require either a VPC peering connection or a private connectivity service, such as xref:networking:configure-privatelink-in-cloud-ui.adoc[AWS PrivateLink], xref:networking:configure-private-service-connect-in-cloud-ui.adoc[GCP Private Service Connect], or xref:networking:azure-private-link.adoc[Azure Private Link]. 
 
 . Click *Create*.
 

diff --git a/modules/get-started/pages/whats-new-cloud.adoc b/modules/get-started/pages/whats-new-cloud.adoc
@@ -6,6 +6,12 @@
 
 This page lists new features added in Redpanda Cloud.
 
+== September 2024
+
+=== Dedicated on Azure: LA
+
+Redpanda now supports xref:get-started:cluster-types/dedicated/create-dedicated-cloud-cluster-aws.adoc[Dedicated clusters on Azure]. This is a limited availability (LA) release for Dedicated clusters. 
+
 == July 2024
 
 === Redpanda Cloud docs
@@ -14,7 +20,7 @@ The https://docs.redpanda.com/home/[Redpanda Docs site] has been redesigned for
 
 === BYOC on Azure: LA
 
-Redpanda now supports xref:get-started:cluster-types/byoc/create-byoc-cluster-azure.adoc[BYOC clusters on Azure]. This is a limited availability (LA) release for BYOC clusters. Additional functionality is expected when this is generally available.
+Redpanda now supports xref:get-started:cluster-types/byoc/create-byoc-cluster-azure.adoc[BYOC clusters on Azure]. This is a limited availability (LA) release for BYOC clusters. 
 
 === Enhancements to Serverless: LA 
 

diff --git a/modules/reference/partials/tiers.adoc b/modules/reference/partials/tiers.adoc
@@ -109,6 +109,7 @@ When you create a Dedicated cluster, you select your usage tier. Each tier provi
 
 [NOTE]
 ====
+* On Azure, tiers 1-3 are supported. 
 * Depending on the workload, it may not be possible to achieve all maximum values. For example, a high number of partitions may make it more difficult to reach the maximum value in throughput.
 * Logical partition counts assume the Redpanda Cloud default replication factor of 3. If you set a higher replication factor, the maximum value for partitions will be lower.
 * Connections are regulated per broker for best performance. For example, in a tier 1 cluster with 3 brokers, there could be up to 3,000 connections per broker. 
@@ -159,5 +160,16 @@ Amazon Web Services (AWS)::
 | us-west-2
 |===
 --
+Azure::
++
+--
+|=== 
+| Region
+
+| East US 
+| North Europe
+| UK South
+|===
+--
 ====
 endif::[]