DOC-136 Document feature Azure Implementation for Cloud GA #353
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
Important Review skippedAuto incremental reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the 📝 WalkthroughWalkthroughThe changes update Redpanda Cloud documentation to reflect the general availability (GA) of Azure BYOVNet (Bring Your Own Virtual Network) clusters. References to "Dedicated and BYOC for Azure" and "Azure Private Link" are removed from limited availability lists, and "BYOVNet for Azure" is removed from beta feature lists. A new section announces the GA of Azure BYOVNet clusters. The Azure Private Link documentation is significantly expanded with clarifying notes, detailed procedural instructions, and explicit command examples. The metadata indicating beta status is removed from the Azure BYOVNet documentation page. Sequence Diagram(s)sequenceDiagram
participant User
participant Documentation
participant Redpanda Cloud API
participant Azure CLI
User->>Documentation: Reads updated Azure BYOVNet/Private Link docs
User->>Redpanda Cloud API: Creates network/cluster (using documented curl commands)
Redpanda Cloud API-->>User: Returns operation status and details
User->>Azure CLI: Executes resource group, VNet, and Private Link endpoint creation
Azure CLI-->>User: Confirms resource and DNS setup
User->>Documentation: Follows step-by-step instructions for configuration
Assessment against linked issues
Assessment against linked issues: Out-of-scope changesNo out-of-scope changes found. Possibly related PRs
Suggested reviewers
✨ Finishing Touches🧪 Generate unit tests
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed 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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
✅ Deploy Preview for rp-cloud ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (4)
modules/get-started/pages/cloud-overview.adoc(0 hunks)modules/get-started/pages/cluster-types/byoc/azure/vnet-azure.adoc(1 hunks)modules/get-started/pages/whats-new-cloud.adoc(1 hunks)modules/networking/pages/azure-private-link.adoc(0 hunks)
💤 Files with no reviewable changes (2)
- modules/get-started/pages/cloud-overview.adoc
- modules/networking/pages/azure-private-link.adoc
🧰 Additional context used
🧠 Learnings (3)
📓 Common learnings
Learnt from: micheleRP
PR: redpanda-data/cloud-docs#267
File: modules/manage/pages/maintenance.adoc:63-64
Timestamp: 2025-04-25T01:42:09.318Z
Learning: The timeline for major upgrade notifications (180 days in advance) was intentionally removed from the Redpanda Cloud maintenance documentation, even though it was mentioned in the PR objectives.
Learnt from: micheleRP
PR: redpanda-data/cloud-docs#267
File: modules/manage/pages/maintenance.adoc:91-92
Timestamp: 2025-04-25T01:41:57.162Z
Learning: The notification timeline for Redpanda Cloud deprecations has been deliberately removed from the documentation, even though the PR summary mentioned a 180-day advance notice period.
Learnt from: david-yu
PR: redpanda-data/cloud-docs#338
File: modules/get-started/pages/cluster-types/byoc/azure/vnet-azure.adoc:74-75
Timestamp: 2025-06-24T03:31:29.345Z
Learning: User david-yu indicated that the standard Azure zones format using plain numbers like "1", "2", "3" is not valid for their specific Azure BYOVNet setup, suggesting there may be specific tooling or API requirements that expect region-prefixed zone names like "centralus-az1".
Learnt from: micheleRP
PR: redpanda-data/cloud-docs#334
File: modules/networking/partials/psc-api2.adoc:15-16
Timestamp: 2025-06-18T21:02:38.074Z
Learning: In the Redpanda Cloud documentation system, cross-reference anchors using the format `#patch-/v1/clusters/-cluster.id-` work correctly for referencing API endpoints, even with dashes instead of curly braces around parameter names.
modules/get-started/pages/cluster-types/byoc/azure/vnet-azure.adoc (1)
Learnt from: david-yu
PR: redpanda-data/cloud-docs#338
File: modules/get-started/pages/cluster-types/byoc/azure/vnet-azure.adoc:74-75
Timestamp: 2025-06-24T03:31:29.345Z
Learning: User david-yu indicated that the standard Azure zones format using plain numbers like "1", "2", "3" is not valid for their specific Azure BYOVNet setup, suggesting there may be specific tooling or API requirements that expect region-prefixed zone names like "centralus-az1".
modules/get-started/pages/whats-new-cloud.adoc (3)
Learnt from: micheleRP
PR: redpanda-data/cloud-docs#267
File: modules/manage/pages/maintenance.adoc:91-92
Timestamp: 2025-04-25T01:41:57.162Z
Learning: The notification timeline for Redpanda Cloud deprecations has been deliberately removed from the documentation, even though the PR summary mentioned a 180-day advance notice period.
Learnt from: micheleRP
PR: redpanda-data/cloud-docs#267
File: modules/manage/pages/maintenance.adoc:63-64
Timestamp: 2025-04-25T01:42:09.318Z
Learning: The timeline for major upgrade notifications (180 days in advance) was intentionally removed from the Redpanda Cloud maintenance documentation, even though it was mentioned in the PR objectives.
Learnt from: micheleRP
PR: redpanda-data/cloud-docs#334
File: modules/networking/partials/psc-api2.adoc:15-16
Timestamp: 2025-06-18T21:02:38.074Z
Learning: In the Redpanda Cloud documentation system, cross-reference anchors using the format `#patch-/v1/clusters/-cluster.id-` work correctly for referencing API endpoints, even with dashes instead of curly braces around parameter names.
🔇 Additional comments (1)
modules/get-started/pages/cluster-types/byoc/azure/vnet-azure.adoc (1)
3-3: Beta flag removed – verify that no residual “beta/LA” language remainsThe
:page-beta:attribute was successfully removed, but double-check the body for any lingering wording that still calls the feature beta or limited availability so readers don’t get mixed messages.
paulohtb6
approved these changes
Jul 11, 2025
david-yu
approved these changes
Jul 17, 2025
…n-for-Cloud-GA # Conflicts: # modules/get-started/pages/cloud-overview.adoc # modules/get-started/pages/whats-new-cloud.adoc # modules/networking/pages/azure-private-link.adoc
…n-for-Cloud-GA # Conflicts: # modules/get-started/pages/whats-new-cloud.adoc
micheleRP
deleted the
DOC-136-Document-feature-Azure-Implementation-for-Cloud-GA
branch
This was referenced Aug 19, 2025
Merged
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This pull request includes updates to feature statuses, removal of outdated feature flags, and enhancements to the clarity of BYOC/BYOVPC/BYOVNet feature descriptions.
Updates to feature statuses:
modules/get-started/pages/whats-new-cloud.adoc: Added announcements for the general availability (GA) of BYOC on Azure and BYOVPC on AWS.*modules/get-started/pages/cloud-overview.adoc: Updated the list of features in limited availability and beta, removing outdated entries and adding new features such as AI agents and Secrets Management.Enhancements to BYOC/BYOVPC/BYOVNet descriptions:
modules/get-started/pages/cluster-types/byoc/azure/vnet-azure.adoc: Updated the description of BYOVNet for Azure, highlighting the benefits of control and managed identities. Added a similar note about add-on feature requirements.*modules/get-started/pages/cluster-types/byoc/aws/vpc-byo-aws.adoc: Improved the description of BYOVPC for AWS, emphasizing control and security benefits. Added a note that BYOVPC is an add-on feature requiring additional purchase.modules/get-started/pages/cluster-types/byoc/gcp/vpc-byo-gcp.adoc: Clarified the BYOVPC feature for GCP, including details about service accounts and permissions.Minor adjustments:
modules/networking/pages/azure-private-link.adoc: Updated a note to specify that Azure Private Link configuration applies to new clusters.modules/get-started/pages/cluster-types/create-dedicated-cloud-cluster.adoc: Removed outdated instructions for unlocking features on Azure. [1] [2]Resolves https://redpandadata.atlassian.net/browse/DOC-136
Review deadline:
Page previews
What's New
Cloud Overview beta/LA features
Create BYOVNet Cluster on Azure
Create BYOVPC Cluster on AWS
Checks