From b5ecff6d915cea71945f50eb7243d1a9c0ef4aec Mon Sep 17 00:00:00 2001 From: mmitoraj Date: Thu, 20 Feb 2025 10:39:49 +0100 Subject: [PATCH 1/3] docs: Add Azure limitation for VPC peering --- docs/user/00-30-vpc-peering.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/user/00-30-vpc-peering.md b/docs/user/00-30-vpc-peering.md index c127aebb..35b5ae67 100644 --- a/docs/user/00-30-vpc-peering.md +++ b/docs/user/00-30-vpc-peering.md @@ -28,9 +28,13 @@ Before you initiate VPC peering from a Kyma cluster, you must perform the follow AwsVpcPeering CR, GcpVpcPeering CR, or AzureVpcPeering CR are cluster-level resources. Once a VPC peering resource is applied, the status of the VPC peering connection is reflected in that CR. At the same time, Cloud Manager creates a VPC peering connection in the Kyma cluster underlying cloud provider landscape and accepts the VPC peering connection in the remote cloud provider landscape. +When you delete a VPC peering CR, the VPC peering connection in the Kyma cloud provider landscape is deleted automatically. However, the remote VPC peering connection is left hanging, and you must delete it manually. + +### Limitations + The limit on the number of VPC peering CRs per Kyma cluster depends on the quotas for each cloud provider. -When you delete a VPC peering CR, the VPC peering connection in the Kyma cloud provider landscape is deleted automatically. However, the remote VPC peering connection is left hanging, and you must delete it manually. +For Microsoft Azure, changes to the address space are not synced between the Kyma and remote VPC networks. If you resize the remote VPC network address space, the Cloud Manager module can't route traffic to it. In this case, you must delete the existing AzureVpcPeering CR and create a new one. ## Related Information From 0132b49269d6d7a2daf93049a3e1d884b7dea2eb Mon Sep 17 00:00:00 2001 From: mmitoraj Date: Thu, 20 Feb 2025 11:15:44 +0100 Subject: [PATCH 2/3] Apply Vladimir's suggestions --- docs/user/00-30-vpc-peering.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user/00-30-vpc-peering.md b/docs/user/00-30-vpc-peering.md index 35b5ae67..1b029bb0 100644 --- a/docs/user/00-30-vpc-peering.md +++ b/docs/user/00-30-vpc-peering.md @@ -34,7 +34,7 @@ When you delete a VPC peering CR, the VPC peering connection in the Kyma cloud p The limit on the number of VPC peering CRs per Kyma cluster depends on the quotas for each cloud provider. -For Microsoft Azure, changes to the address space are not synced between the Kyma and remote VPC networks. If you resize the remote VPC network address space, the Cloud Manager module can't route traffic to it. In this case, you must delete the existing AzureVpcPeering CR and create a new one. +For Microsoft Azure, changes to the address space are not synced between the Kyma and remote VPC networks. If you resize the remote VPC network address space, routs are out of sync. In this case, you must delete the existing AzureVpcPeering CR and create a new one. ## Related Information From d6b2bb6cab8d3e00e2b223d96bd87800b7b82c49 Mon Sep 17 00:00:00 2001 From: mmitoraj Date: Thu, 20 Feb 2025 13:16:53 +0100 Subject: [PATCH 3/3] Fix --- docs/user/00-30-vpc-peering.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user/00-30-vpc-peering.md b/docs/user/00-30-vpc-peering.md index 1b029bb0..99153f0d 100644 --- a/docs/user/00-30-vpc-peering.md +++ b/docs/user/00-30-vpc-peering.md @@ -34,7 +34,7 @@ When you delete a VPC peering CR, the VPC peering connection in the Kyma cloud p The limit on the number of VPC peering CRs per Kyma cluster depends on the quotas for each cloud provider. -For Microsoft Azure, changes to the address space are not synced between the Kyma and remote VPC networks. If you resize the remote VPC network address space, routs are out of sync. In this case, you must delete the existing AzureVpcPeering CR and create a new one. +For Microsoft Azure, changes to the address space are not synced between the Kyma and remote VPC networks. If you resize the remote VPC network address space, routes are out of sync. In this case, you must delete the existing AzureVpcPeering CR and create a new one. ## Related Information