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 <[email protected]> * return Delete cluster section * minor edit * minor edit * Update modules/get-started/partials/no-access.adoc Co-authored-by: Jake Cahill <[email protected]> --------- Co-authored-by: David Yu <[email protected]> Co-authored-by: Jake Cahill <[email protected]>
redpanda-data · Dec 19, 2024 · 6ffc240 · 6ffc240
1 parent 991a22d
commit 6ffc240
Show file tree

Hide file tree

Showing 8 changed files with 16 additions and 1 deletion.
diff --git 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
@@ -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
@@ -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
@@ -144,6 +144,8 @@ Replace the following placeholders:
 - `<cluster-id>`: Enter the cluster ID listed in the Redpanda Cloud UI. Go to the Cluster Overview page, and look in the Details section.
 - `<token>`: 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
@@ -453,4 +453,6 @@ After that completes, run:
 
 ```bash
 rpk cloud byoc azure destroy --redpanda-id ${REDPANDA_ID}
-```
+```
+
+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
@@ -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
@@ -534,3 +534,5 @@ rpk cloud byoc gcp apply --redpanda-id='<redpanda-id>' --project-id='<service-pr
 . Click *Next*. 
 
 . On the *Deploy* page, similar to standard BYOC clusters, log in to Redpanda Cloud and deploy the agent.
+
+include::partial$no-access.adoc[]
diff --git a/modules/get-started/partials/no-access.adoc b/modules/get-started/partials/no-access.adoc
@@ -0,0 +1 @@
+NOTE: Redpanda Cloud does not support user access to the control plane with `kubectl`. This restriction allows Redpanda Data to manage all configuration changes internally to ensure a 99.99% service level agreement (SLA) for BYOC clusters.
-Original file line number
+Diff line change
@@ Expand Up / @@ -338,3 +338,5 @@ After that completes, run: @@
     ```bash
     rpk cloud byoc aws destroy --redpanda-id ${REDPANDA_ID}
     ```
+    include::partial$no-access.adoc[]
Original file line number	Diff line number	Diff line change
Expand Up		@@ -534,3 +534,5 @@ rpk cloud byoc gcp apply --redpanda-id='<redpanda-id>' --project-id='<service-pr
		. Click Next.

		. On the Deploy page, similar to standard BYOC clusters, log in to Redpanda Cloud and deploy the agent.

		include::partial$no-access.adoc[]
Original file line number	Diff line number	Diff line change
		@@ -0,0 +1 @@
		NOTE: Redpanda Cloud does not support user access to the control plane with `kubectl`. This restriction allows Redpanda Data to manage all configuration changes internally to ensure a 99.99% service level agreement (SLA) for BYOC clusters.