Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows 1909 support #2339

Merged
merged 4 commits into from
Jun 18, 2020
Merged

Conversation

michaelbeaumont
Copy link
Contributor

@michaelbeaumont michaelbeaumont commented Jun 17, 2020

Description

Closes #2321

Checklist

  • Added tests that cover your change (if possible)
  • Added/modified documentation as required (such as the README.md, or the userdocs directory)
  • Manually tested
  • Added labels for change area (e.g. area/nodegroup), target version (e.g. version/0.12.0) and kind (e.g. kind/improvement)
  • Make sure the title of the PR is a good description that can go into the release notes

return imageFamily == NodeImageFamilyWindowsServer2019CoreContainer || imageFamily == NodeImageFamilyWindowsServer2019FullContainer
return imageFamily == NodeImageFamilyWindowsServer2019CoreContainer ||
imageFamily == NodeImageFamilyWindowsServer2019FullContainer ||
imageFamily == NodeImageFamilyWindowsServer1909CoreContainer
Copy link
Contributor

@cPu1 cPu1 Jun 17, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alternatively:

switch imageFamily {
case NodeImageFamilyWindowsServer2019CoreContainer, NodeImageFamilyWindowsServer2019FullContainer, NodeImageFamilyWindowsServer1909CoreContainer:
    return true
default:
    return false
}

Comment on lines 48 to 50
case api.NodeImageFamilyWindowsServer2019CoreContainer,
api.NodeImageFamilyWindowsServer2019FullContainer,
api.NodeImageFamilyWindowsServer1909CoreContainer:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since this case clause has grown a bit, I think we should now use isWindowsImage.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

fixed, IsWindowsImage now in default case

Comment on lines 196 to 198
case api.NodeImageFamilyWindowsServer2019FullContainer,
api.NodeImageFamilyWindowsServer2019CoreContainer,
api.NodeImageFamilyWindowsServer1909CoreContainer:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above, I think we should use isWindowsImage here.

@michaelbeaumont michaelbeaumont requested a review from cPu1 June 17, 2020 12:54
@michaelbeaumont
Copy link
Contributor Author

@cPu1 I had to update the test but I changed them to not be dependent on the exact AMI names, what do you think?

@cPu1
Copy link
Contributor

cPu1 commented Jun 18, 2020

@cPu1 I had to update the test but I changed them to not be dependent on the exact AMI names, what do you think?

Makes sense. We are going to eventually deprecate static resolution for AMIs, so those tests will be removed as well.

@michaelbeaumont michaelbeaumont merged commit a7fc5f6 into eksctl-io:master Jun 18, 2020
@michaelbeaumont michaelbeaumont deleted the win1909 branch June 18, 2020 10:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Windows 1909 AMI support for tag --node-ami-family
2 participants