From 6ffc240c8534614980096bb1b44a353c47dc5924 Mon Sep 17 00:00:00 2001 From: Michele Cyran Date: Thu, 19 Dec 2024 08:32:17 -0700 Subject: [PATCH] Doc-84 RP doesn't support accessing managed deployments via kubectl (#159) * DOC-84 BYOC doesn't support kubectl * minor edit * Update modules/get-started/pages/cluster-types/byoc/azure/vnet-azure.adoc Co-authored-by: David Yu * return Delete cluster section * minor edit * minor edit * Update modules/get-started/partials/no-access.adoc Co-authored-by: Jake Cahill <45230295+JakeSCahill@users.noreply.github.com> --------- Co-authored-by: David Yu Co-authored-by: Jake Cahill <45230295+JakeSCahill@users.noreply.github.com> --- modules/get-started/pages/cloud-overview.adoc | 2 ++ .../pages/cluster-types/byoc/aws/create-byoc-cluster-aws.adoc | 2 ++ .../get-started/pages/cluster-types/byoc/aws/vpc-byo-aws.adoc | 2 ++ .../cluster-types/byoc/azure/create-byoc-cluster-azure.adoc | 2 ++ .../pages/cluster-types/byoc/azure/vnet-azure.adoc | 4 +++- .../pages/cluster-types/byoc/gcp/create-byoc-cluster-gcp.adoc | 2 ++ .../get-started/pages/cluster-types/byoc/gcp/vpc-byo-gcp.adoc | 2 ++ modules/get-started/partials/no-access.adoc | 1 + 8 files changed, 16 insertions(+), 1 deletion(-) create mode 100644 modules/get-started/partials/no-access.adoc diff --git a/modules/get-started/pages/cloud-overview.adoc b/modules/get-started/pages/cloud-overview.adoc index 4c40f2bc..a51d6feb 100644 --- a/modules/get-started/pages/cloud-overview.adoc +++ b/modules/get-started/pages/cloud-overview.adoc @@ -205,6 +205,8 @@ either a public endpoint or a VPC peering network connection. Sensitive data and image::shared:d_c_plane.png[Data plane and control plane] +include::partial$no-access.adoc[] + A BYOC cluster is initially set up from the control plane. This is a two-step process performed by `rpk cloud byoc apply`: . You bootstrap a virtual machine (VM) in your VPC. diff --git a/modules/get-started/pages/cluster-types/byoc/aws/create-byoc-cluster-aws.adoc b/modules/get-started/pages/cluster-types/byoc/aws/create-byoc-cluster-aws.adoc index f735e6a4..dae556b2 100644 --- a/modules/get-started/pages/cluster-types/byoc/aws/create-byoc-cluster-aws.adoc +++ b/modules/get-started/pages/cluster-types/byoc/aws/create-byoc-cluster-aws.adoc @@ -44,6 +44,8 @@ Optionally, click *Advanced settings* to specify up to five key-value custom tag + As part of agent deployment, Redpanda assigns the permission required to run the agent. For details about these permissions, see xref:security:authorization/cloud-iam-policies.adoc[AWS IAM policies]. +include::partial$no-access.adoc[] + == Next steps xref:networking:byoc/aws/index.adoc[Configure private networking] diff --git a/modules/get-started/pages/cluster-types/byoc/aws/vpc-byo-aws.adoc b/modules/get-started/pages/cluster-types/byoc/aws/vpc-byo-aws.adoc index d93eb7c5..5ea304f2 100644 --- a/modules/get-started/pages/cluster-types/byoc/aws/vpc-byo-aws.adoc +++ b/modules/get-started/pages/cluster-types/byoc/aws/vpc-byo-aws.adoc @@ -338,3 +338,5 @@ After that completes, run: ```bash rpk cloud byoc aws destroy --redpanda-id ${REDPANDA_ID} ``` + +include::partial$no-access.adoc[] diff --git a/modules/get-started/pages/cluster-types/byoc/azure/create-byoc-cluster-azure.adoc b/modules/get-started/pages/cluster-types/byoc/azure/create-byoc-cluster-azure.adoc index b0474cc1..efcab0ac 100644 --- a/modules/get-started/pages/cluster-types/byoc/azure/create-byoc-cluster-azure.adoc +++ b/modules/get-started/pages/cluster-types/byoc/azure/create-byoc-cluster-azure.adoc @@ -144,6 +144,8 @@ Replace the following placeholders: - ``: Enter the cluster ID listed in the Redpanda Cloud UI. Go to the Cluster Overview page, and look in the Details section. - ``: Enter the API token you received in step 1. +include::partial$no-access.adoc[] + == Next steps xref:networking:azure-private-link.adoc[] diff --git a/modules/get-started/pages/cluster-types/byoc/azure/vnet-azure.adoc b/modules/get-started/pages/cluster-types/byoc/azure/vnet-azure.adoc index 26ae51f3..8aed882c 100644 --- a/modules/get-started/pages/cluster-types/byoc/azure/vnet-azure.adoc +++ b/modules/get-started/pages/cluster-types/byoc/azure/vnet-azure.adoc @@ -453,4 +453,6 @@ After that completes, run: ```bash rpk cloud byoc azure destroy --redpanda-id ${REDPANDA_ID} -``` \ No newline at end of file +``` + +include::partial$no-access.adoc[] diff --git a/modules/get-started/pages/cluster-types/byoc/gcp/create-byoc-cluster-gcp.adoc b/modules/get-started/pages/cluster-types/byoc/gcp/create-byoc-cluster-gcp.adoc index 63a4f13c..3dee54d1 100644 --- a/modules/get-started/pages/cluster-types/byoc/gcp/create-byoc-cluster-gcp.adoc +++ b/modules/get-started/pages/cluster-types/byoc/gcp/create-byoc-cluster-gcp.adoc @@ -32,6 +32,8 @@ Optionally, click *Advanced settings* to specify up to five key-value custom lab + Note that `rpk` configures the permissions required by the agent to provision and actively maintain the cluster. For details about these permissions, see xref:security:authorization/cloud-iam-policies-gcp.adoc[GCP IAM permissions]. +include::partial$no-access.adoc[] + == Next steps xref:networking:byoc/gcp/index.adoc[Configure private networking] diff --git a/modules/get-started/pages/cluster-types/byoc/gcp/vpc-byo-gcp.adoc b/modules/get-started/pages/cluster-types/byoc/gcp/vpc-byo-gcp.adoc index f622970e..b17c2889 100644 --- a/modules/get-started/pages/cluster-types/byoc/gcp/vpc-byo-gcp.adoc +++ b/modules/get-started/pages/cluster-types/byoc/gcp/vpc-byo-gcp.adoc @@ -534,3 +534,5 @@ rpk cloud byoc gcp apply --redpanda-id='' --project-id='