-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
containerd: always use config_path #11755
containerd: always use config_path #11755
Conversation
/ok-to-test |
config_path was introduced in containerd 1.5.0, and registry.mirrors is deprecated. There is no reason to keep the old alternative, so just always use config_path, and consequently remove the option.
b0611f9
to
a342a64
Compare
Thanks @VannTen ! lgtm |
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: MrFreezeex, VannTen The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
config_path was introduced in containerd 1.5.0, and registry.mirrors is deprecated. There is no reason to keep the old alternative, so just always use config_path, and consequently remove the option.
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
config_path was introduced in containerd 1.5.0, and registry.mirrors is
deprecated.
There is no reason to keep the old alternative, so just always use
config_path, and consequently remove the option.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Ideally we would have first defaulted to config_path before removing the option, but I don't think there is a downside.
It's up for discussion though if I missed some shortcomings (in that case I will only default to true)
Does this PR introduce a user-facing change?: