Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
[azurerm_kubernetes_cluster ] - support for the
windows_profile
property #3519[azurerm_kubernetes_cluster ] - support for the
windows_profile
property #3519Changes from all commits
554cc1f
6604193
3937492
afada79
904fc51
6677cbc
9e0049a
2c9c088
254433e
50ce4ba
572fdaa
3c65f5f
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we add this logic back in?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not Really:
The VNET is not mandatory anymore
That's why I deleted it
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Correct, AKS with windows required Azure CNI, and now, the AzureCNI doesn't require a custom VNET / Subnet to be provided.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
based on this comment: https://github.com/Azure/acs-engine/pull/2168/files#diff-f45af0b14c127459636440a5981a6934R823
this is still valid for linux clusters, and is planned to come to Windows, so perhaps we need to add this back in with an
if !windows
check?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It appears this wasn't added back in?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@katbyte @tombuildsstuff Are you sure you want it bacK ? The test was removed more than one year ago: Azure/acs-engine#2322
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tombuildsstuff was mentioning it is still required for linux clusters and that linked issue only refers to windows.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the customVnet is supported, we are currently using it with hybrid cluster.
looks at the latest code:
https://github.com/jackfrancis/acs-engine/blob/master/pkg/api/vlabs/validate.go#L609-L651
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Azure/acs-engine#2322 this when it was reverted. which shows that customVnet is supported with Windows