Managed_vnet_to_vnet_injection automation#42
Conversation
|
Hi @josecisneros04 |
There was a problem hiding this comment.
Hi @josecisneros04
Please add prerequisites such as :
Permissions: The customer (Cx) must possess sufficient privileges to deploy the required Azure resources. (Object Owner for current workspace as well as new VNET)
Downtime: This conversion requires planned downtime. Due to the complexity of a potential rollback, allocate ample time for the activity.
Private Link (PL) Endpoints: Private Link endpoints cannot be hosted on the subnets delegated to the Databricks workspace. A separate subnet must be used for hosting PL endpoints.
Subnet Usage: Use subnets that are not currently in use by other Databricks workspaces to avoid potential deployment errors.
Please also add post deployment test :
Upon successful deployment, you will observe that the Networking settings in your workspace are no longer grayed out.
Spin up a compute resource (cluster).
Locate the corresponding Virtual Machine (VM) in Azure using the cluster name in its tags.
Confirm that the VM is running within the VNet and subnets specified during the VNet injection process.
Pull Request
Description
Brief description of what this PR does and why.
Category
Type of Change
Project Details
Project Name:
Managed_vnet_to_vnet_injection automation
Purpose:
Updates Managed VNET for customization of networking
Technologies Used:
Powershell
Testing
Security Compliance ✅
By submitting this PR, I confirm I have followed the CONTRIBUTING.md guidelines and security requirements.