-
Notifications
You must be signed in to change notification settings - Fork 313
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
AKS will start rejecting requests with unknown AgentPool mode starting on 2025-01-01 #4468
Comments
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. |
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. |
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. |
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. |
Starting on January 1, 2025, invalid values sent to the Azure AKS API for the
properties.mode
field of AKS AgentPools will be rejected.Prior to this change, unknown modes were assumed to be
User
.The only valid values for this field are the (case-sensitive) strings: "User", "System", or "Gateway".
Note: “Gateway” is currently in the preview API.
The text was updated successfully, but these errors were encountered: