If you've reconfigured your IPv4 CIDR blocks, you may need to update the vSwitch associated with your Realtime Compute for Apache Flink workspace. This keeps your workspace communicating correctly within your virtual private cloud (VPC).
Usage notes
-
Adding a vSwitch automatically enables high availability for the gateway cluster. This action is irreversible. After it is enabled, you cannot reduce the number of vSwitches.
-
Before you change a vSwitch, add the CIDR block of the new vSwitch to the whitelists of your upstream and downstream storage services to ensure network connectivity.
Prerequisites
Before you begin, make sure you have:
-
A Realtime Compute for Apache Flink workspace
-
A target vSwitch that meets both of the following requirements:
-
Resides in the same VPC as your workspace
-
Is in a zone supported by Realtime Compute for Apache Flink
-
Change the vSwitch
-
Add the CIDR block of the new vSwitch to the whitelists of your upstream and downstream storage services.
-
Log on to the Realtime Compute for Apache Flink console.
-
Find the workspace, then in the Actions column, choose More > Modify vSwitches.
-
In the Modify vSwitches dialog box, select the vSwitch you want to use. If the vSwitch you need is not listed, click Create vSwitch in the note at the top of the dialog box. After creating the vSwitch, click
in the upper-left corner of the list to refresh the dialog box, then select the new vSwitch.
-
Click OK.
A message appears indicating that the vSwitch modification has started. The workspace enters the Configuring state and automatically returns to the Running state in about 30 seconds, at which point the vSwitch modification is complete.
What's next
By default, Realtime Compute for Apache Flink cannot access the Internet. To enable Internet access, create a NAT gateway in your VPC and add a source network address translation (SNAT) entry that binds your workspace's vSwitch to an elastic IP address (EIP). For details, see FAQ about network connectivity.