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.
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
Enable k8s reserved cpus #3964
Enable k8s reserved cpus #3964
Changes from all commits
241b187
7cb2390
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
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.
Don't we need to limit this for k8s only? And have a conditional here to perform a
Noop
migration?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 couldn't find any example of that for an "Add a new setting" migration.
I found
https://github.com/bottlerocket-os/bottlerocket/blob/1.20.x/sources/api/migration/migrations/v1.20.0/add-ntp-default-options-v0-1-0/src/main.rs
and
https://github.com/bottlerocket-os/bottlerocket/blob/1.19.x/sources/api/migration/migrations/v1.19.2/add-ecs-enable-container-metadata/src/main.rs
and
https://github.com/bottlerocket-os/bottlerocket/blob/1.19.x/sources/api/migration/migrations/v1.19.0/add-additional-ecs-settings/src/main.rs
all of which do the same as mine...
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.
bottlerocket/sources/api/migration/migrations/archived/v1.15.0/oci-defaults-docker-setting/src/main.rs
Line 2 in a1bcca5
The example I linked to used
?
but I don't think it is required.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 tried a few conbinations of this and the other change you linked to.
I'm stuck on...
... any hints?
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.
Oh, sorry, there was a typo in my suggestion, there should not be a ; at the end of the first migration call to end the statement.
The error is complaining about mixing and matching statements vs an expression. In this case, if you leave off the
;
it will return the results of the function call, in this casemigration()
so want both statements to not have;
but then you also don't wantOk(())
at the end of yourrun()
function. So the code I used to get this to compile looks like this for the entire file: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.
Either this suggestion, or adding
?;
andOk(())
at the end should be enough.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.
This migration looks fine to me - it doesn't matter that
aws-ecs-*
doesn't have these settings, it'll just be a no-op on downgrade because the paths won't exist.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 only need a conditional migration in the case where settings are added in one version for some variants (
aws-k8s-*
) and then in a subsequent version for other variants (aws-ecs-*
). These settings won't ever be added foraws-ecs-*
so it's fine.