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

Remove unused fields from type "AgentPoolProfile". #914

Merged

Conversation

yizhang4321
Copy link
Member

No description provided.

CustomKubeletConfig *CustomKubeletConfig `json:"customKubeletConfig,omitempty"`
CustomLinuxOSConfig *CustomLinuxOSConfig `json:"customLinuxOSConfig,omitempty"`
Name string `json:"name"`
Count int `json:"count"`
Copy link
Contributor

Choose a reason for hiding this comment

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

question: for this PR, we are only removing parameters that are not populated in paramsMap - correct?

I could be wrong but I think Count is one of those that get written to the map but aren't actually used anywhere.

Copy link
Member Author

Choose a reason for hiding this comment

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

Thanks for the info. Yeah, you are right, this PR only removes the easy, obvious ones. Once this goes in, I'll look into "Count". If as you mentioned it is not used, I'll remove it.

@yizhang4321 yizhang4321 merged commit a63a562 into Azure:master Jul 8, 2021
@yizhang4321 yizhang4321 deleted the yizhang4321/RemoveUnusedFields branch July 8, 2021 21:47
CustomNodeLabels map[string]string `json:"customNodeLabels,omitempty"`
PreprovisionExtension *Extension `json:"preProvisionExtension"`
KubernetesConfig *KubernetesConfig `json:"kubernetesConfig,omitempty"`
AvailabilityZones []string `json:"availabilityZones,omitempty"`
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think we're using this anywhere are we?

Copy link
Member Author

Choose a reason for hiding this comment

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

Thanks for the info. I will go through them and remove unused ones in future PRs.

"name": "nodepool1",
"orchestratorVersion": "1.19.3",
Copy link
Contributor

Choose a reason for hiding this comment

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

Just to clarify, are we removing agentPoolProfile.orchestratorVersion because we have the same field as properties. orchestratorProfile.orchestratorVersion already present?

Copy link
Member Author

Choose a reason for hiding this comment

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

The orchestratorVersion version in AgentPoolProfile is never used in AgentBaker, thus I removed it.

Copy link
Contributor

@adilliadil adilliadil left a comment

Choose a reason for hiding this comment

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

LGTM, let's just make sure the e2es on RP change passes with these changes in Agentbaker

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants