-
Notifications
You must be signed in to change notification settings - Fork 460
Ensure all agent pool parameters are preserved in managed cluster creates #5521
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -23,6 +23,12 @@ import ( | |
| "strings" | ||
|
|
||
| asocontainerservicev1 "github.com/Azure/azure-service-operator/v2/api/containerservice/v1api20231001" | ||
| // NOTE: when the hub API version is updated, verify the | ||
| // ManagedClusterAgentPoolProfile below has every field defined. If a field | ||
| // isn't defined, the agent pool will be created with a zero/null value, and | ||
| // then updated to the user-defined value. If the field is immutable, this | ||
| // update will fail. The linter should catch if there are missing fields, | ||
| // but verify that check is actually working. | ||
| asocontainerservicev1hub "github.com/Azure/azure-service-operator/v2/api/containerservice/v1api20240901/storage" | ||
| "k8s.io/apimachinery/pkg/apis/meta/v1/unstructured" | ||
| clusterv1 "sigs.k8s.io/cluster-api/api/v1beta1" | ||
|
|
@@ -350,12 +356,14 @@ func setAgentPoolProfilesFromAgentPools(managedCluster conversion.Convertible, a | |
| ScaleDownMode: hubPool.Spec.ScaleDownMode, | ||
| ScaleSetEvictionPolicy: hubPool.Spec.ScaleSetEvictionPolicy, | ||
| ScaleSetPriority: hubPool.Spec.ScaleSetPriority, | ||
| SecurityProfile: hubPool.Spec.SecurityProfile, | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The main alternative to this approach is to use unkeyed struct fields and let the compiler check that everything is defined, but I think I prefer the sanity check of having both field names on one line like this. |
||
| SpotMaxPrice: hubPool.Spec.SpotMaxPrice, | ||
| Tags: hubPool.Spec.Tags, | ||
| Type: hubPool.Spec.Type, | ||
| UpgradeSettings: hubPool.Spec.UpgradeSettings, | ||
| VmSize: hubPool.Spec.VmSize, | ||
| VnetSubnetReference: hubPool.Spec.VnetSubnetReference, | ||
| WindowsProfile: hubPool.Spec.WindowsProfile, | ||
| WorkloadRuntime: hubPool.Spec.WorkloadRuntime, | ||
| } | ||
|
|
||
|
|
||
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.
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.
Most of the new fields here aren't possible to set from an AzureManagedMachinePool, so there's a fair bit of no-op here. I was too lazy to audit which ones can actually be set, but keeping everything here makes for one less thing to worry about in case we do add or remove any features from CAPZ.
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.
ACK, thx for adding the maintenance comments so we're less likely to omit this in the future