Use userdata task to persistent instance metadata routes in AWS#80320
Use userdata task to persistent instance metadata routes in AWS#80320mburke5678 merged 1 commit intoopenshift:mainfrom
Conversation
jrvaldes
left a comment
There was a problem hiding this comment.
@mburke5678 thanks for working on this, PTAL at my suggestion.
modules/windows-machineset-aws.adoc
Outdated
| ==== | ||
| For disconnected clusters, the Windows AMI must have the EC2LaunchV2 agent version 2.0.1643 or later installed. | ||
|
|
||
| For more information on the EC2LaunchV2 agent, see link:https://aws.amazon.com/blogs/modernizing-with-aws/upgrade-ec2launch-v2[Which AMIs have EC2Launch v2?] in the AWS documentation. |
There was a problem hiding this comment.
I'd rather cite the official docs [1] than a blog post.
[1] https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2launch-v2-install.html
|
@arnaik-rh CAn you please assign an appropriate QE resource to review this PR? Thank you in advance. |
|
@arnaik-rh Can you please assign an appropriate QE resource to review this PR? Thank you in advance. |
5d1f027 to
85f97c6
Compare
|
|
||
| |Amazon Web Services (AWS) | ||
| |Windows Server 2019, version 1809 | ||
| a|* Windows Server 2022, OS Build link:https://support.microsoft.com/en-us/topic/april-25-2022-kb5012637-os-build-20348-681-preview-2233d69c-d4a5-4be9-8c24-04a450861a8d[20348.681] or later ^[1]^ |
There was a problem hiding this comment.
🤖 [error] RedHat.CaseSensitiveTerms: Use 'operating system' rather than 'OS'. For more information, see RedHat.CaseSensitiveTerms.
There was a problem hiding this comment.
@mburke5678 I can see why you didn't use the vale bot's advice, it would clutter up the table and that's what the vendors call the build.
|
The This is because your PR targets the If the update in your PR does NOT apply to version 4.18 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main. |
|
/lgtm |
85f97c6 to
a1f548d
Compare
|
New changes are detected. LGTM label has been removed. |
|
@mburke5678: all tests passed! Full PR test history. Your PR dashboard. 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-sigs/prow repository. I understand the commands that are listed here. |
|
/label peer-review-in-progress |
|
|
||
| |Amazon Web Services (AWS) | ||
| |Windows Server 2019, version 1809 | ||
| a|* Windows Server 2022, OS Build link:https://support.microsoft.com/en-us/topic/april-25-2022-kb5012637-os-build-20348-681-preview-2233d69c-d4a5-4be9-8c24-04a450861a8d[20348.681] or later ^[1]^ |
There was a problem hiding this comment.
@mburke5678 I can see why you didn't use the vale bot's advice, it would clutter up the table and that's what the vendors call the build.
|
/label peer-review-done |
|
@GroceryBoyJr: Those labels are not set on the issue: 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-sigs/prow repository. |
|
@GroceryBoyJr Thanks for the review. I should have mentioned about the OS. I did, indeed, leave it as is based on what Windows calls it. Nice catch |
|
/cherrypick enterprise-4.18 |
|
/cherrypick enterprise-4.17 |
|
/cherrypick enterprise-4.16 |
openshift/windows-machine-config-operator#2296
https://issues.redhat.com/browse/WINC-1149
Previews:
Creating a Windows machine set on AWS -> Prereqs -> Third bullet
Sample YAML for a Windows MachineSet object on AWS -> Note after call-out 5
WMCO 10.17.0 supported platforms and Windows Server versions -> Footnote 1
QE review: