AKS will start rejecting requests with unknown fields in the 2024-01-01 API version

[matthchr]

All current AKS API versions silently ignore unknown fields. An unknown field is a field that is not part of the AKS API. Starting in AKS API version 2024-01-01 and 2024-01-02-preview this behavior is changing. Unknown fields in a request will result in the request being rejected with an error stating that we don't understand the unknown field. This change only impacts new API versions and will not impact you unless you update to use an API version 2024-01-01 or later. Existing API calls (via ARM templates or otherwise) will continue to function as-is.

There are a few common possible reasons this happens:

1. Using ARM templates/BICEP, you included a valid field in the right spot, but the template API version was too old and doesn't support that field.
2. Using ARM templates/BICEP, you included a valid named field in the wrong spot in the resource hierarchy (for example, what should have been $.name was instead $.properties.name)
3. Using ARM templates/BICEP, you included an invalid field. There might be a typo in your template (for example, what should have been aadProfile was instead addProfile).
4. You are using a deprecated (and/or very out of date) SDK.

[matthchr]

We recently realized that some customers got a notice for the field storageProfile, or the field mode with userAgent ARM template/BICEP, which was confusing as they didn't use/send that field via any ARM templates they could find. Upon further investigation we realized that the Azure Portal is sending these two unknown fields (storageProfile and mode) field via the ARM templates it uses under the hood. This is a bug in the portal which we're fixing.

If you got a notification about unknown fields for storageProfile or mode and you've used the Azure Portal to create or update a cluster recently, you can ignore the notification. If the notification includes any unknown fields other than storageProfile or mode, you should still look into it and check your ARM/BICEP templates for those non-storageProfile fields and make sure they're in the right location, spelled correctly, and that the templates have specified the correct API version.

[microsoft-github-policy-service]

Action required from @Azure/aks-pm

[microsoft-github-policy-service]

This issue has been automatically marked as stale because it has not had any activity for 60 days. It will be closed if no further activity occurs within 15 days of this comment.

[microsoft-github-policy-service]

This issue will now be closed because it hasn't had any activity for 7 days after stale. matthchr feel free to comment again on the next 7 days to reopen or open a new issue after that time if you still have a question/issue or suggestion.

[matthchr]

Reopening this as it may still be relevant for some users who are just migrating to the 2024 APIs now.

[microsoft-github-policy-service]

This issue has been automatically marked as stale because it has not had any activity for 21 days. It will be closed if no further activity occurs within 7 days of this comment.

[microsoft-github-policy-service]

This issue will now be closed because it hasn't had any activity for 7 days after stale. matthchr feel free to comment again on the next 7 days to reopen or open a new issue after that time if you still have a question/issue or suggestion.

[matthchr]

Reopening once more, will let it be closed after this.

[microsoft-github-policy-service]

This issue has been automatically marked as stale because it has not had any activity for 21 days. It will be closed if no further activity occurs within 7 days of this comment.

[microsoft-github-policy-service]

This issue will now be closed because it hasn't had any activity for 7 days after stale. matthchr feel free to comment again on the next 7 days to reopen or open a new issue after that time if you still have a question/issue or suggestion.