The Cloud Manager module provides managed Virtual Private Cloud (VPC) peering functionality that allows you to peer the Kyma VPC network with a remote VPC network. Virtual network peering is possible only between networks of the same cloud providers. VPC peering in Kyma is fully automated. It means that Cloud Manager configures the peering on both Kyma's and cloud provider's side.
When you configure VPC peering in Kyma, you depend on the cloud provider of your Kyma cluster. The cloud provider in use determines the exact implementation.
The Cloud Manager module supports the VPC Peering feature of the following cloud providers:
- Amazon Web Services VPC peering
- Google Cloud VPC Network Peering
- Microsoft Azure Virtual network peering
You can configure Cloud Manager's VPC peering using a dedicated custom resource (CR) corresponding with the cloud provider for your Kyma cluster, namely AwsVpcPeering CR, GcpVpcPeering CR, or AzureVpcPeering CR.
Before you initiate VPC peering from a Kyma cluster, you must perform the following actions:
- Authorize Cloud Manager in the remote cloud provider landscape. For more information, see Authorizing Cloud Manager in the Remote Cloud Provider
- Tag the remote network with the Kyma shoot name. For more information, see the following tutorials:
AwsVpcPeering CR, GcpVpcPeering CR, or AzureVpcPeering CR are cluster-level resources. Once one of the VPC peering resources is applied, the status of the VPC peering connection is reflected in that CR. The limit of the number of VPC Peering CRs per Kyma cluster depends on the quotas for each cloud provider individually.