Known issues and limitations for cluster networks

Cluster Networks for VPC is available for select customers only. Contact IBM Support if you are interested in using this functionality.

Before you create a cluster network, review the following known issues and limitations.

Known issues

The new instance profiles are expected to take about 20 minutes to start.
When creating an instance using the API, the instance.create Activity Tracker event will be missing if you specify the cluster_network_attachments property. If you want to avoid this, you can create instance cluster network attachments separately.
If a cluster network reserved IP's auto_delete property is set to false, and it is attached to a cluster network interface, any attempt to delete the cluster network will result in it being stuck in a deleting state. To avoid this, before you delete the cluster network itself, first delete the cluster network interfaces, then delete the cluster network reserved IPs. You can also avoid this scenario by updating cluster network reserved IPs and setting the auto_delete property to true.

Cluster network attachments can only be set when the instance is stopped or created.
Cluster network traffic is isolated and cannot be routed outside. Any access to a cluster network must be through an attached instance. As a result, without connectivity between the cluster network and the VPC network, the following resources cannot connect with cluster networks:
Services that are not supported: