Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: Add Azure limitation for VPC peering #1040

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

docs: Add Azure limitation for VPC peering #1040

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
b5ecff6
docs: Add Azure limitation for VPC peering
mmitoraj Feb 20, 2025
0132b49
Apply Vladimir's suggestions
mmitoraj Feb 20, 2025
d6b2bb6
Fix
mmitoraj Feb 20, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion docs/user/00-30-vpc-peering.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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, routes are out of sync. In this case, you must delete the existing AzureVpcPeering CR and create a new one.

## Related Information

Expand Down
Loading