azure: create an image for booting machines for the cluster from vhd blob - #1976
Conversation
|
/test e2e-azure |
2ba4eca to
60ae2d4
Compare
|
/cc @crawford @jhixson74 @imcleod for approval if this is way forward for RHCOS image in Azure. |
887f440 to
01ac37a
Compare
|
/test e2e-azure |
1 similar comment
|
/test e2e-azure |
01ac37a to
dba39b1
Compare
|
/test e2e-azure |
|
/retest |
dba39b1 to
7472266
Compare
|
/test e2e-azure |
|
/test e2e-azure |
|
/approve |
Currently we use a storage account for boot diagnostics for the masters, another one for storing the ignition config for bootstrap node. In the future we might need to store the RHCOS vhd in a storage account, and there is no valid case for these many storage accounts created by installer. And each storage container can have its invidual ACL. Using a single storage account is simpler.
… vhd blob previously the terraform expected an Azure Image [1] provided to the cluster, but that approach had some disadvantages: * the image needed to be created before creating the cluster * the image location was hardcoded to a specific resource-group And since RHCOS isn't avaiable on the Public Registry of images, the new flow is using the vhd blob from Azure storage and creating an Azure Image from it for the cluster. The public vhd is copied to cluster's resource group to make sure the image is not based directly on a public artifact.
Currently the OS image source for Azure was hard coded to `/resourceGroups/rhcos_images/.../rhcos` in rhcos.Image asset which means the image needed to pre-exist in the same sunscription. But now the OS image source for Azure will be a vhd blob in Azure storage account as specified by build pipeline and the machines will be using the image in the cluster's resource group.
7472266 to
8558590
Compare
8558590 to
47edea9
Compare
updated. |
|
/test e2e-azure |
3 similar comments
|
/test e2e-azure |
|
/test e2e-azure |
|
/test e2e-azure |
|
/retest e2e-azure |
|
It's concerning that this is this flakey. @abhinavdahiya do you think azure is more flakey than AWS? |
|
@nstielau I think so, although aws may be having its own issues right now... |
DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/test e2e-azure |
1 similar comment
|
/test e2e-azure |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abhinavdahiya, crawford, jhixson74 The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
4 similar comments
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@abhinavdahiya: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
…_url" Fixing a typo from 5416b42 (data/azure: create an image for booting machines for the cluster from vhd blob, 2019-07-11, openshift#1976).
…_url" Fixing a typo from 5416b42 (data/azure: create an image for booting machines for the cluster from vhd blob, 2019-07-11, openshift#1976).

previously the terraform expected an Azure Image [1] provided to the cluster, but that approach had some disadvantages:
And since RHCOS isn't avaiable on the Public Registry of images, the new flow is using the vhd blob from Azure storage and creating an Azure Image from it for the cluster.