Skip to content

Conversation

@micheleRP
Copy link
Contributor

@micheleRP micheleRP commented Jun 18, 2025

Description

This pull request introduces significant updates to the documentation for configuring GCP Private Service Connect (PSC) in Redpanda Cloud. The changes focus on restructuring content, improving clarity, and consolidating redundant information into reusable partials. Additionally, new files were added to provide dedicated guides for PSC configuration in both the Cloud UI and API.

Key Changes

Separate pages for GCP Private Service Connect on Dedicated:

  • Added modules/networking/pages/dedicated/gcp/configure-psc-in-ui.adoc to provide a focused guide on setting up PSC using the Redpanda Cloud UI.
  • Added modules/networking/pages/dedicated/gcp/configure-psc-in-api.adoc to document how to configure PSC using the Cloud API, including detailed steps for creating clusters and enabling PSC.
  • Removed details from files like modules/networking/pages/configure-private-service-connect-in-cloud-ui.adoc and modules/networking/pages/gcp-private-service-connect.adoc. These files were replaced with references to the new partials. [1] [2] [3]

Minor Improvements:

  • Standardized syntax for external links and references, such as updating the jq installation link syntax in modules/networking/pages/azure-private-link.adoc.
  • Removed an outdated placeholder note from modules/networking/pages/dedicated/gcp/vpc-peering-gcp.adoc.

Documentation Restructuring and Consolidation:

  • Updated navigation links in modules/ROOT/nav.adoc to reflect the new file structure for PSC-related documentation. Old links were replaced with new, more descriptive paths (configure-psc-in-ui.adoc and configure-psc-in-api.adoc).
  • Consolidated redundant PSC content into reusable partials (psc-api.adoc and psc-api2.adoc), which now centralize shared information about requirements, notes, and testing steps. [1] [2]

Resolves https://redpandadata.atlassian.net/browse/DOC-1457
Review deadline:

Page previews

BYOC PSC in UI
BYOC PSC in API
Dedicated PSC in UI
Dedicated PSC in API
AWS PrivateLink in API

Checks

  • New feature
  • Content gap
  • Support Follow-up
  • Small fix (typos, links, copyedits, etc)

@micheleRP micheleRP requested a review from a team as a code owner June 18, 2025 20:32
@netlify
Copy link

netlify bot commented Jun 18, 2025

Deploy Preview for rp-cloud ready!

Name Link
🔨 Latest commit d94caee
🔍 Latest deploy log https://app.netlify.com/projects/rp-cloud/deploys/68543835f1404700087ea45d
😎 Deploy Preview https://deploy-preview-334--rp-cloud.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jun 18, 2025

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

📝 Walkthrough

Walkthrough

This set of changes restructures and updates the documentation for configuring Google Cloud Platform (GCP) Private Service Connect (PSC) within Redpanda Cloud, specifically for dedicated environments. It introduces new modular documentation pages and partials for both UI-based and API-based PSC configuration, updates navigation links to point to these new resources, and removes or simplifies older, monolithic guides. Minor clarifications and formatting updates are also included in related networking documentation, while no changes are made to exported or public code entities.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Redpanda Cloud UI
    participant Redpanda Cloud API
    participant GCP (gcloud CLI)

    User->>Redpanda Cloud UI: Select resource group, export ID
    User->>GCP (gcloud CLI): Create VPC firewall rules for PSC
    User->>Redpanda Cloud API: POST /v1/networks (create network resource)
    Redpanda Cloud API-->>User: Return network ID
    User->>Redpanda Cloud API: POST /v1/clusters (enable PSC, provide accept list)
    Redpanda Cloud API-->>User: Return cluster info
    User->>GCP (gcloud CLI): Monitor service attachment creation
    User->>Redpanda Cloud UI: (Alternative) Enable PSC via UI, follow guided steps
    User->>GCP (gcloud CLI): (Alternative) Create consumer-side resources, DNS, etc.
Loading

Assessment against linked issues

Objective Addressed Explanation
Update documentation to refer to dedicated clusters instead of BYOVPC clusters (DOC-1457)

Assessment against linked issues: Out-of-scope changes

No out-of-scope changes found.

Possibly related PRs

Suggested reviewers

  • Feediver1
  • paulzhang97

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🔭 Outside diff range comments (1)
modules/networking/pages/gcp-private-service-connect.adoc (1)

11-14: Fix Asciidoc step formatting
The step to copy the Resource Group ID is missing the leading list marker, which breaks the ordered list. It should start with a dot (.).
Apply this diff:

- Copy and store the resource group ID (UUID) from the URL in the browser.
+ . Copy and store the resource group ID (UUID) from the URL in the browser.
🧹 Nitpick comments (10)
modules/networking/partials/psc-api.adoc (1)

11-11: Fix grammatical error in note block.

The sentence at line 11 is missing a verb and comma; suggest rephrasing for clarity.

-As of February 2025 ability to allow requests from Private Service Connect endpoints to stay within the same AZ, avoiding additional networking costs. To upgrade, contact https://support.redpanda.com/hc/en-us/requests/new[Redpanda Support^].
+As of February 2025, you can allow requests from Private Service Connect endpoints to stay within the same AZ, avoiding additional networking costs. To upgrade, contact https://support.redpanda.com/hc/en-us/requests/new[Redpanda Support^].
modules/ROOT/nav.adoc (1)

49-51: Ensure link text matches page title.

The dedicated GCP UI page title includes “GCP Private Service Connect”, but the nav link omits “GCP”. For consistency, align the link text with the page title:

- **** xref:networking:dedicated/gcp/configure-psc-in-ui.adoc[Configure Private Service Connect in the Cloud UI]
+ **** xref:networking:dedicated/gcp/configure-psc-in-ui.adoc[Configure GCP Private Service Connect in the Cloud UI]

- **** xref:networking:dedicated/gcp/configure-psc-in-api.adoc[Configure Private Service Connect with the Cloud API]
+ **** xref:networking:dedicated/gcp/configure-psc-in-api.adoc[Configure GCP Private Service Connect with the Cloud API]
modules/networking/pages/gcp-private-service-connect.adoc (2)

22-39: Consistent code block syntax
You’re using [,bash] to annotate the GCP CLI examples. For better syntax highlighting, switch to the standard Asciidoctor syntax:

-[,bash]
+ [source,bash]
----
gcloud compute networks subnets create ...
----

85-87: Clarify placeholder section styling
The “Replace the following placeholder variables for the request body:” line is introduced correctly, but the removed -- markers may leave an orphaned horizontal rule. Ensure you fully remove or replace them with proper list delimiters so the list renders as intended.

modules/networking/partials/psc-ui.adoc (4)

2-8: Clarify terminology in NOTE block
The first bullet references “Private Service” but should explicitly say “Private Service Connect” for clarity. Also verify the cross-reference path (xref:networking:gcp-private-service-connect.adoc) resolves correctly.


37-45: Break up long commands for readability
The NAT subnet creation snippet is valid but dense. Splitting flags onto separate lines improves scannability:

[source,bash]
----
gcloud compute networks subnets create <subnet-name> \
  --project <host-project-id> \
  --network <shared-vpc-name> \
  --region <region> \
  --range <subnet-range> \
  --purpose PRIVATE_SERVICE_CONNECT
----

47-57: Improve firewall rule formatting
The firewall CLI packs many ports into one --allow flag. For maintainability, break out ports or use an inline list:

[source,bash]
----
gcloud compute firewall-rules create redpanda-psc \
  --description "Allow access to Redpanda PSC endpoints" \
  --allow tcp:30181,tcp:30282,... \
  --source-ranges 10.0.0.0/8,172.16.0.0/12,...
----

59-66: Ensure placeholder list renders correctly
The placeholder section uses hyphens for bullets, which is acceptable, but confirm there's a blank line before it so Asciidoctor treats it as a list. Optionally switch to * bullets for consistency with other docs.

modules/networking/pages/dedicated/gcp/configure-psc-in-api.adoc (2)

18-30: Use standard Asciidoctor code block syntax
For the GCP firewall example, replace [,bash] with [source,bash] to enable proper syntax highlighting:

-[,bash]
+ [source,bash]
----
gcloud compute firewall-rules create redpanda-psc \
  ...
----

60-68: Ensure placeholder list renders correctly
The "Replace the following placeholder variables" section should have a blank line before the list and could use * bullets for consistency:

Replace the following placeholder variables for the request body:

* `<shared-vpc-name>`: ...
* `<region>`: ...
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 79da45b and a17cf2c.

📒 Files selected for processing (10)
  • modules/ROOT/nav.adoc (1 hunks)
  • modules/networking/pages/azure-private-link.adoc (1 hunks)
  • modules/networking/pages/configure-private-service-connect-in-cloud-ui.adoc (1 hunks)
  • modules/networking/pages/dedicated/gcp/configure-psc-in-api.adoc (1 hunks)
  • modules/networking/pages/dedicated/gcp/configure-psc-in-ui.adoc (1 hunks)
  • modules/networking/pages/dedicated/gcp/vpc-peering-gcp.adoc (0 hunks)
  • modules/networking/pages/gcp-private-service-connect.adoc (2 hunks)
  • modules/networking/partials/psc-api.adoc (1 hunks)
  • modules/networking/partials/psc-api2.adoc (1 hunks)
  • modules/networking/partials/psc-ui.adoc (1 hunks)
💤 Files with no reviewable changes (1)
  • modules/networking/pages/dedicated/gcp/vpc-peering-gcp.adoc
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: Redirect rules - rp-cloud
  • GitHub Check: Header rules - rp-cloud
  • GitHub Check: Pages changed - rp-cloud
🔇 Additional comments (9)
modules/networking/pages/azure-private-link.adoc (1)

22-22: External link syntax standardized for jq.

The AsciiDoc external link for jq has been reformatted to match our style. Ensure this renders correctly in the published docs.

modules/networking/pages/dedicated/gcp/configure-psc-in-ui.adoc (1)

1-5: Well-structured UI configuration page.

The page correctly delegates content to the psc-ui.adoc partial and sets the env-dedicated attribute. No issues found.

modules/networking/pages/configure-private-service-connect-in-cloud-ui.adoc (1)

1-6: Streamlined BYOC UI page looks good.

Switching to include the psc-ui.adoc partial and setting env-byoc is correct; the page is concise and maintains its original aliases.

modules/networking/pages/gcp-private-service-connect.adoc (2)

4-6: Verify environment conditional for BYOVPC content
The :env-byoc: true attribute enables the BYOVPC-specific instructions under ifdef::env-byoc[]. Confirm this flag is set consistently in related pages (e.g., the UI partial) and remove it if the content should apply universally.


260-260: Approve inclusion of psc-api2.adoc partial
Ending the page with include::networking:partial$psc-api2.adoc[] cleanly injects the remaining API instructions (testing & disabling). This keeps the documentation modular.

modules/networking/partials/psc-ui.adoc (2)

32-34: Verify the BYOVPC conditional block
The ifdef::env-byoc[] guard is used correctly for BYOVPC instructions. Ensure a matching endif::[] is present below and consider adding a brief comment above the guard to explain its purpose.


67-68: Close conditional block and check link syntax
The link to GCP docs and the closing endif::[] are in place. Verify the caret notation in [creating a subnet for Private Service Connect^] renders as expected.

modules/networking/pages/dedicated/gcp/configure-psc-in-api.adoc (2)

1-6: Verify dedicated environment conditional
The :env-dedicated: true attribute correctly scopes this page to dedicated cluster workflows. Confirm alignment with other dedicated docs and remove it if the content also applies to non-dedicated scenarios.


157-157: Approve inclusion of psc-api2.adoc partial
Appending include::networking:partial$psc-api2.adoc[] integrates the final API steps for testing and teardown, keeping the guide modular.

@simon0191
Copy link
Member

@micheleRP I just noticed we have the same issue in AWS.
image

Copy link
Contributor

@david-yu david-yu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM did a quick scan and I agree with the changes

Copy link
Contributor

@kbatuigas kbatuigas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm!

@micheleRP micheleRP merged commit c9e5bc6 into main Jun 23, 2025
5 checks passed
@micheleRP micheleRP deleted the DOC-1457-Dedicated-private-service-connect-docs-say-create-a-BYOVPC-cluster-instead-of-a-dedicated-cluster branch June 23, 2025 20:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants