-
Notifications
You must be signed in to change notification settings - Fork 705
Add cdc improved private link document. #21929
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add cdc improved private link document. #21929
Conversation
|
Hi @ginkgoch. Thanks for your PR. I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Summary of ChangesHello @ginkgoch, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request significantly enhances and clarifies the documentation for configuring private network connectivity for TiDB Cloud changefeeds. It introduces a unified guide for setting up private endpoints, which is then referenced and integrated into the existing documentation for sinking data to both self-hosted Apache Kafka and MySQL. This change aims to simplify the user experience by providing a consistent and comprehensive approach to private link configurations across different cloud providers and downstream services. Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here. You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension. Footnotes
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This pull request introduces a new, centralized document for setting up private endpoints for changefeeds, which simplifies the documentation for Kafka and MySQL sinks. The changes are a positive step towards better organization. My review focuses on improving clarity, consistency, and adherence to the style guide. I've provided suggestions for using sentence case in titles, employing active voice, ensuring consistent terminology, and correcting minor typos and formatting issues to enhance the overall quality of the documentation.
| <div label="Private Endpoint"> | ||
| Private Connect leverages **Private Link** or **Private Service Connect** technologies from cloud providers to enable resources in your VPC to connect to services in other VPCs using private IP addresses, as if those services were hosted directly within your VPC. | ||
|
|
||
| - Ensure your MySQL service is connective though private endpoint. Provide the following information in the TiDB Cloud console to create the changefeed: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's a typo here. 'connective though' should be 'connectable through'. Also, the sentence can be rephrased to be more direct and use active voice, as recommended by the style guide.1
| - Ensure your MySQL service is connective though private endpoint. Provide the following information in the TiDB Cloud console to create the changefeed: | |
| - To connect through a private endpoint, provide the following information in the TiDB Cloud console to create the changefeed: |
Style Guide References
Footnotes
-
Repository Style Guide, lines 22, 43-45: Write in second person ("you") and avoid passive voice. ↩
| * If using **VPC Peering** or **Public IP**, fill in your MySQL endpoint. | ||
| * If using **Private Endpoint**, select the **Sink Private Endpoint** which is prepared in the [Network](#network) section. | ||
|
|
||
| 4. Fill in the MySQL endpoints, user name, and password in **MySQL Connection**. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the MySQL endpoint is already provided in step 3 for VPC Peering/Public IP, and a Sink Private Endpoint is used for the other option, asking for 'MySQL endpoints' again here is redundant and confusing. It's better to only ask for the credentials.
| 4. Fill in the MySQL endpoints, user name, and password in **MySQL Connection**. | |
| 4. Fill in the user name and password in **MySQL Connection**. |
| title: Setup Private Endpoint for Changefeed | ||
| summary: Learn how to setup a private endpoint for Changefeed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
According to the style guide, titles should use sentence case.1 Also, 'setup' as a verb should be two words ('set up'), and 'Changefeed' should be lowercase for consistency with other documents.2
| title: Setup Private Endpoint for Changefeed | |
| summary: Learn how to setup a private endpoint for Changefeed. | |
| title: Set up a private endpoint for changefeed | |
| summary: Learn how to set up a private endpoint for changefeed. |
Style Guide References
Footnotes
| summary: Learn how to setup a private endpoint for Changefeed. | ||
| --- | ||
|
|
||
| # Setup Private Endpoint for Changefeed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
According to the style guide, headings should use sentence case.1 Also, 'Setup' as a verb should be two words ('set up'), and 'Changefeed' should be lowercase for consistency.2
| # Setup Private Endpoint for Changefeed | |
| # Set up a private endpoint for changefeed |
Style Guide References
Footnotes
| 3. Fill in the **Service Attachment** that you have configured in [Setup Self Hosted Kafka Private Service Connect in Google Cloud](/tidb-cloud/setup-self-hosted-kafka-private-service-connect.md) | ||
| 4. Fill in the **Bootstrap Ports**. It is recommended that you provide more than one port. You can use commas `,` to separate multiple ports. | ||
| 5. Select an **Authentication** option according to your Kafka authentication configuration. | ||
| 2. Select the **Sink Private Endpoint** which is prepared in the [Network](#network) section. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To follow the style guide's preference for active voice, it's better to rephrase 'which is prepared'.1
| 2. Select the **Sink Private Endpoint** which is prepared in the [Network](#network) section. | |
| 2. Select the **Sink Private Endpoint** that you prepared in the [Network](#network) section. |
Style Guide References
Footnotes
-
Repository Style Guide, lines 22, 43-45: Write in second person ("you") and avoid passive voice. ↩
| </div> | ||
| </SimpleTab> | ||
|
|
||
| ## Step 1. Open the Private Endpoint for Changefeed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This heading is a bit ambiguous. A clearer heading that describes the action would be better. Also, headings should be in sentence case per the style guide.1
| ## Step 1. Open the Private Endpoint for Changefeed | |
| ## Step 1. Open the private endpoint creation page |
Style Guide References
Footnotes
-
Repository Style Guide, line 32: Use sentence case for headings (e.g.,
## Configure the cluster). ↩
| 2. Navigate to the cluster overview page of the TiDB cluster, then click **Settings** > **Networking**. | ||
| 3. Click **Create Private Endpoint** in the **Private Endpoint for Changefeed** section. | ||
|
|
||
| ## Step 2. Configure the Private Endpoint for Changefeed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
According to the style guide, headings should use sentence case.1
| ## Step 2. Configure the Private Endpoint for Changefeed | |
| ## Step 2. Configure the private endpoint for changefeed |
Style Guide References
Footnotes
-
Repository Style Guide, line 32: Use sentence case for headings (e.g.,
## Configure the cluster). ↩
|
|
||
| 3. Enter the **Endpoint Service Name** that you configured in [Set Up Self-Hosted Kafka Private Link Service in AWS](https://docs.pingcap.com/tidbcloud/setup-aws-self-hosted-kafka-private-link-service/). | ||
|
|
||
| 4. Select the **Number of Availability Zones**. Make sure you select the same **Number of AZs** and **AZ IDs** as your Kafka deployment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The style guide recommends direct instructions.1 Rephrasing 'Make sure you select' to a more direct command would be better.
| 4. Select the **Number of Availability Zones**. Make sure you select the same **Number of AZs** and **AZ IDs** as your Kafka deployment. | |
| 4. Select the **Number of Availability Zones**. Ensure the **Number of AZs** and **AZ IDs** are the same as your Kafka deployment. |
Style Guide References
Footnotes
-
Repository Style Guide, line 22: Write in second person ("you") when addressing users. ↩
|
|
||
| 2. Enter a **Name** for this **Private Endpoint**. | ||
|
|
||
| 3. Enter the **Service Attachment** that you configured in [Setup Self Hosted Kafka Private Service Connect in Google Cloud](https://docs.pingcap.com/tidbcloud/setup-self-hosted-kafka-private-service-connect/). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For consistency, 'Setup' should be 'Set up' to match the verb form used elsewhere. While this is part of a link to another document, it's good practice to maintain consistency across the documentation set.
| 3. Enter the **Service Attachment** that you configured in [Setup Self Hosted Kafka Private Service Connect in Google Cloud](https://docs.pingcap.com/tidbcloud/setup-self-hosted-kafka-private-service-connect/). | |
| 3. Enter the **Service Attachment** that you configured in [Set up Self Hosted Kafka Private Service Connect in Google Cloud](https://docs.pingcap.com/tidbcloud/setup-self-hosted-kafka-private-service-connect/). |
|
|
||
|
|
||
|
|
||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
|
||
| ## Restrictions | ||
|
|
||
| - Only Organization Owner and Project Owner roles can create private endpoints for changefeeds. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now the project dev role also has the permission.
Co-authored-by: WangLe1321 <[email protected]>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
|
@WangLe1321: adding LGTM is restricted to approvers and reviewers in OWNERS files. In response to this: Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
91a43ae to
ffa3906
Compare
Co-authored-by: xixirangrang <[email protected]>
Co-authored-by: xixirangrang <[email protected]>
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: qiancai The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
First-time contributors' checklist
What is changed, added or deleted? (Required)
Which TiDB version(s) do your changes apply to? (Required)
Tips for choosing the affected version(s):
By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.
For details, see tips for choosing the affected versions.
What is the related PR or file link(s)?
Do your changes match any of the following descriptions?