Known issues for cluster networks

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

• 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 cluster network attachments separately.

• 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:

  • Floating IPs
  • Load balancers
  • Private Path services
  • Public gateways
  • Virtual Private Endpoint gateways
  • VPNs

• Services that are not supported:

  • Flow logs
  • Network ACLs
  • Routing tables
  • Secondary IPs
  • Security groups