You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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):
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
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
The text was updated successfully, but these errors were encountered:
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):
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
The text was updated successfully, but these errors were encountered: