-
Notifications
You must be signed in to change notification settings - Fork 522
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
Control container v0.6.3 #2472
Control container v0.6.3 #2472
Conversation
4d5804f
to
62c4df7
Compare
@@ -15,4 +15,4 @@ superpowered = false | |||
|
|||
[metadata.settings.host-containers.control.source] | |||
setting-generator = "schnauzer settings.host-containers.control.source" | |||
template = "{{ ecr-prefix settings.aws.region }}/bottlerocket-control:v0.6.1" | |||
template = "{{ ecr-prefix settings.aws.region }}/bottlerocket-control:v0.6.3" |
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.
Nit: Same as in the other PR, probably a note on why we updated from 0.6.1
to 0.6.3
will help!
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.
As a best practice, Bottlerocket should always be running the latest host containers as (in addition to new features) they'll have a more up-to-date base image containing any security fixes and package updates since the previous release. For deeper dives, I would just check the release notes of the container repos themselves.
62c4df7
to
91b7e53
Compare
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.
🥾
Description of changes:
Update and migrate from control container v0.6.1 to v0.6.3.
0.6.3
Testing done:
Coming soon!Tested this pr along with #2471 using testsys.
Migration test passed successfully.
Terms of contribution:
By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.