Skip to content

Latest commit

 

History

History
69 lines (49 loc) · 4.33 KB

04-40-10-azure-vpc-peering.md

File metadata and controls

69 lines (49 loc) · 4.33 KB
Raw

AzureVpcPeering Custom Resource

The azurevpcpeering.cloud-resources.kyma-project.io custom resource (CR) specifies the virtual network peering between Kyma and the remote Azure Virtual Private Cloud (VPC) network. Virtual network peering is only possible within the networks of the same cloud provider.

Once an AzureVpcPeering CR is created and reconciled, the Cloud Manager controller creates a VPC peering connection in the VPC network of the Kyma cluster in the underlying cloud provider subscription, and accepts a VPC peering connection in the remote cloud provider subscription.

Authorization

Cloud Manager must be authorized in the remote cloud provider subscription to accept a VPC peering connection.

Use the following table to identify Cloud Manager service principal based on your Kyma landscape:

BTP cockpit URL Kyma dashboard URL Cloud Manager service principal
https://canary.cockpit.btp.int.sap https://dashboard.stage.kyma.cloud.sap kyma-cloud-manager-peering-stage
https://emea.cockpit.btp.cloud.sap https://dashboard.kyma.cloud.sap kyma-cloud-manager-peering-prod

And assign the following Identity and Access Management (IAM) roles to the Cloud Manager service principal:

  • Classic Network Contributor
  • Network Contributor

Deleting AzureVpcPeering

Kyma's underlying cloud provider VPC peering connection is deleted as a part of the AzureVpcPeering deletion. The remote VPC peering connection is left hanging, and you must delete it manually.

Specification

This table lists the parameters of the given resource together with their descriptions:

Spec:

Parameter Type Description
remotePeeringName string Specifies the name of the VNet peering in the remote subscription.
remoteVnet string Specifies the ID of the VNet in the remote subscription.

Status:

Parameter Type Description
id string Represents the VPC peering name on the Kyma cluster underlying cloud provider subscription.
state string Signifies the current state of CustomObject.
conditions []object Represents the current state of the CR's conditions.
conditions.lastTransitionTime string Defines the date of the last condition status change.
conditions.message string Provides more details about the condition status change.
conditions.reason string Defines the reason for the condition status change.
conditions.status (required) string Represents the status of the condition. The value is either True, False, or Unknown.
conditions.type string Provides a short description of the condition.

Sample Custom Resource

See an exemplary AzureVpcPeering custom resource:

apiVersion: cloud-resources.kyma-project.io/v1beta1
kind: AzureVpcPeering
metadata:
  name: peering-to-my-vnet
spec:
  remotePeeringName: peering-to-my-kyma
  remoteVnet: /subscriptions/afdbc79f-de19-4df4-94cd-6be2739dc0e0/resourceGroups/MyResourceGroup/providers/Microsoft.Network/virtualNetworks/MyVnet