Skip to content

Update Microsoft.ContainerService managedClusters API version to 2024-02-01#552

Merged
lonegunmanb merged 3 commits intoAzure:mainfrom
olofmattsson-inriver:patch/azapi_update_resource_version
Jun 4, 2024
Merged

Update Microsoft.ContainerService managedClusters API version to 2024-02-01#552
lonegunmanb merged 3 commits intoAzure:mainfrom
olofmattsson-inriver:patch/azapi_update_resource_version

Conversation

@olofmattsson-inriver
Copy link
Copy Markdown
Contributor

Describe your changes

Support for Azure Kubernetes 2023-01-02-preview API is ending 20 June 2024. Update to the latest stable version.

Issue number

@zioproto
Copy link
Copy Markdown
Contributor

This is a valid issue

Screenshot 2024-05-29 at 13 59 13

according to:
https://learn.microsoft.com/en-us/azure/templates/microsoft.containerservice/allversions

the latest API version is correctly 2024-02-01

@lonegunmanb could we please merge this asap ? thanks

Copy link
Copy Markdown
Member

@lonegunmanb lonegunmanb left a comment

Choose a reason for hiding this comment

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

Thanks @olofmattsson-inriver for opening this pr to us! I have a question for the API version you assigned.

Comment thread main.tf Outdated
count = can(var.http_proxy_config.no_proxy[0]) ? 1 : 0

type = "Microsoft.ContainerService/managedClusters@2023-01-02-preview"
type = "Microsoft.ContainerService/managedClusters@2024-02-01-preview"
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

You've assigned two different API for two aks update resources, do we have any special reason for this?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

No other than my ignorance. My test passed so I didn't spot the typo. Updated the PR

@lonegunmanb
Copy link
Copy Markdown
Member

Hi @olofmattsson-inriver the e2e test failed, but I checked the error message, I believe we have fixed the issue which caused error in our latest main branch. Would you please rebase your branch with our latest main branch and try again? Thanks!

@olofmattsson-inriver
Copy link
Copy Markdown
Contributor Author

Hi @lonegunmanb. I've rebased and hopefully, this will fix the issue.

@lonegunmanb
Copy link
Copy Markdown
Member

I'm going to merge this pr despite e2e test failure, since after a review I'm sure that the failure was caused by our fragile tests.

Copy link
Copy Markdown
Member

@lonegunmanb lonegunmanb left a comment

Choose a reason for hiding this comment

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

Thanks @olofmattsson-inriver , LGTM!

@lonegunmanb lonegunmanb merged commit 81526f9 into Azure:main Jun 4, 2024
@olofmattsson-inriver olofmattsson-inriver deleted the patch/azapi_update_resource_version branch June 4, 2024 05:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

3 participants