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 upgrade path from Azure CNI to Azure CNI Overlay #26260base: main
Are you sure you want to change the base?
azurerm_kubernetes_cluster
: Support for upgrade path from Azure CNI to Azure CNI Overlay #26260Changes from 1 commit
a81a846
92d0b43
d43f7cf
1fc34b8
4513485
8185135
23036f3
58789aa
066f275
67d4db8
904cd30
c033c7e
5299adf
a7011a3
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.
Although this will work for upgrading from Azure CNI to Azure CNI Overlay, it will cause issues for users that are using other networking configurations which we still need to support.
pod_cidr
andpod_cidrs
are bothOptional
andComputed
because there are instances where the API will assign values to these if they're omitted e.g. when usingkubenet
, this compounds with the fact that these value change checks performed in theCustomizeDiff
compare the old state value and the new state value and not whether the value in the users configuration has changed.Ultimately this will end up triggering a
ForceNew
for users that are still usingkubenet
but haven't specifiedpod_cidr
orpod_cidrs
(and potentially other scenarios!).I would appreciate if you could add some test cases (or extend existing test cases) to ensure that we're not triggering a
ForceNew
in situations where we shouldn't be, those should also help you to refine the condition needed here to enable the behaviour you're after without introducing unwanted side effects.