-
Notifications
You must be signed in to change notification settings - Fork 5.7k
Mikolaj/add custom node config 2023 06 02 preview #24539
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
FumingZhang
merged 5 commits into
Azure:FumingZhang-containerservice-Microsoft.ContainerService-2023-06-02-preview
from
UtheMan:mikolaj/add-custom-node-config-2023-06-02-preview
Jun 25, 2023
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
2a64ff3
feat: add Ulimit config and updated sysctl ranges to swagger
21db7ac
fix: use ulimits in json of LinuxOSConfig
3502f2b
feat: add response example
9496737
fix: add ulimits to custom words
7d074d8
Revert "fix: add ulimits to custom words"
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
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
All the changes for minimum/maximum were not there before, hence they are getting reported as broken changes (even though new ranges are bigger than the limits we enforced before)
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.
We could also remove these range changes to avoid breaking errors, no preference.
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.
Consult with @FumingZhang, but IMO it's OK to add these as they are bigger than the old actual limits enforced by the old RP. Also happy to remove if we don't want to deal with breaking change pain it adds, but if we do decide to remove we should consider putting it into the documentation manually what the min/max values are.
Uh oh!
There was an error while loading. Please reload this page.
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.
There will be more changes to custom node config in the coming months, I could add all the limitations to swagger then, to avoid adding it only to select few parameters.
So now I'd remove them for easier merge of those changes and re-add them with new changes in the coming months, thoughts? @matthchr @FumingZhang
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.
We should in theory be able to get this merged without too much issue as is, IMO. But really defer to what @FumingZhang thinks/wants here. My 2c is keep them.
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.
Thanks Matthew! Will wait for Fuming's opinion.
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.
I think it's ok to have such a breaking change, will go through the breaking change review once I create the PR based on the dev branch later.