Skip to content
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

Missing manual steps in PrivateLink config #2627

Closed
WanYixian opened this issue Sep 20, 2024 · 0 comments · Fixed by #2630
Closed

Missing manual steps in PrivateLink config #2627

WanYixian opened this issue Sep 20, 2024 · 0 comments · Fixed by #2630
Assignees
Labels
cloud documentation Improvements or additions to documentation

Comments

@WanYixian
Copy link
Contributor

WanYixian commented Sep 20, 2024

Related code PR

No response

Which part(s) of the docs might be affected or should be updated? And how?

Currently, our PrivateLink feature doesn’t work out of box for Confluent private Kafka clusters. Two extra steps needs to be performed (manually):

  1. Before provisioning a RW PrivateLink, we need to make sure the Availability Zones of their cluster is a subset of the Availability Zones RisingWave offers for PrivateLink provisioning
  2. We need to manually add DNS records for the PrivateLink after the it’s provisioned.
    Before we can automate these steps, add some explanations to the existing PrivateLink doc and ask user to contact us first if they plan to use the PrivateLink to connect to a Confluent Cloud cluster.

Reference

No response

@WanYixian WanYixian added documentation Improvements or additions to documentation cloud labels Sep 20, 2024
@WanYixian WanYixian self-assigned this Sep 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cloud documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant