Bug 2084547 - [4.10] update azure arm templates to support customer provided vnet
Summary: [4.10] update azure arm templates to support customer provided vnet
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.z
Assignee: Johnny Liu
QA Contact: Johnny Liu
Depends On: 2084539
TreeView+ depends on / blocked
Reported: 2022-05-12 12:12 UTC by Johnny Liu
Modified: 2022-05-23 13:25 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 2084539
Last Closed: 2022-05-23 13:25:13 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift installer pull 5892 0 None open Bug 2084547: update azure arm templates to support customer provided vnet 2022-05-12 12:16:17 UTC
Red Hat Product Errata RHBA-2022:2258 0 None None None 2022-05-23 13:25:17 UTC

Description Johnny Liu 2022-05-12 12:12:38 UTC
+++ This bug was initially created as a clone of Bug #2084539 +++

Per the azure upi arm templates in https://github.com/openshift/installer/tree/master/upi/azure, it assumes the vnet is always created from 01_vnet.json with the same basename from infra id. 

Actually for some special cases, vnet maybe provisioned in advanced, UPI process will skip vnet creation step, e.g: https://github.com/openshift/release/pull/27977, create other resources in the provided customer vnet. 

So we need to update the existing templates to introduce a new optional parameter - vnetBaseName for that.


$ openshift-install version
<your output here>



Please specify:
* UPI (semi-manual installation on customized infrastructure)

What happened?

Comment 5 errata-xmlrpc 2022-05-23 13:25:13 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Container Platform 4.10.15 bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.