Update UPI vSphere terraform code for v0.12#2057
Update UPI vSphere terraform code for v0.12#2057DanyC97 wants to merge 1 commit intoopenshift:masterfrom
Conversation
|
Hi @DanyC97. Thanks for your PR. I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: DanyC97 The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Route53 is still being used for DNS, isn't it?
There was a problem hiding this comment.
that is correct @vrutkovs is still used hence why i've moved it up in the pre-req section so folks know upfront what is required from the existing code base.
I can extend if y'all okay with to mention why R53 provider is used and not DNS provider, let me know
|
/test e2e-vsphere |
|
/ok-to-test |
|
job failed due to sounds like you not able to import the template into your vCenter env |
|
/hold we are close (almost in) feature freeze, cannot make these changes until there's an exception. |
no problem at all, totally understand ! let me know when you are out the freeze mode, happy to carry on from there |
There was a problem hiding this comment.
Is 'Dani/' prepended to the folder path why the tests fail? You probably don't want this included in the PR?
628ec2f to
f3b6f8c
Compare
|
@abhinavdahiya i saw you started to work on #2396 , can i assume we can re-activate this PR ? |
|
@abhinavdahiya gentle reminder, please let me know if you are still interested in this PR now that 4.2 is out. If not then please close this PR. |
|
Hey, |
@mkelnermishal happy to continue the work if @abhinavdahiya confirm he is ready/ happy to accept the PR, haven't received any feedback on my previous attempts to get an answer hence my assumption is that is not needed |
|
/test e2e-vsphere |
|
@DanyC97: PR needs rebase. 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. |
|
Thanks for the changes! And I think it's important that we move to 0.12 terraform.. So here's the pickle, the baremetal using packet.net here also uses the terraform.. and the image we use to test both is 0.11 so we will have to either make sure: B) we update all the changes in one PR. |
@abhinavdahiya thank you for taking the time to respond and refocus attention on this PR. I'm easy going with either of the 2 suggestions. What does the baremetal team prefer to go with? |
|
maybe merge the effort in one PR with #2479 or chain them one after another or just be aware of it ;) |
I would prefer the option B. if you can help migrate the metal work with vsphere work to 0.12. I can help review and get it merged... |
|
@DanyC97: 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. |
This PR updates the UPI vSphere terraform templates to v0.12.
Ref #1936 (comment)
@abhinavdahiya @staebler @vrutkovs please help review it.