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
Mark commandline parameters related to dockershim as deprecated #98730
Mark commandline parameters related to dockershim as deprecated #98730
Conversation
/assign @SergeyKanzhelev @sjenning |
/sig node |
/priority important-soon |
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 approve
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.
/triage accepted
0eac1ca
to
c558272
Compare
pkg/kubelet/config/flags.go
Outdated
@@ -95,15 +95,23 @@ func (s *ContainerRuntimeOptions) AddFlags(fs *pflag.FlagSet) { | |||
fs.StringVar(&s.DockershimRootDirectory, "experimental-dockershim-root-directory", s.DockershimRootDirectory, "Path to the dockershim root directory.") | |||
fs.MarkHidden("experimental-dockershim-root-directory") | |||
fs.StringVar(&s.PodSandboxImage, "pod-infra-container-image", s.PodSandboxImage, fmt.Sprintf("The image whose network/ipc namespaces containers in each pod will use. %s", dockerOnlyWarning)) | |||
fs.MarkDeprecated("pod-infra-container-image", "will be removed along with dockershim.") |
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.
if we remove this one with docker-shim, We need some way to get information about sandbox image from container runtime #81756.
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.
@adisky indeed. let's track that as a new issue, we may prefer another flag as this one started with docker and then was co-opted by gc manager if i remember correctly.
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 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.
+1 on re-using the flag because of GC.
eventually CRI implementers should dump their info properly the way containerd is doing today on it's socket - you can try crictl info
for that.
but currently not e.g. cri-o and dockershim.
at that point we can deprecate this flag, if we don't want to allow the override.
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.
Removed the deprecation from this flag. improved the description as well.
c558272
to
96ecba2
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.
/lgtm
@dims from verify: |
Signed-off-by: Davanum Srinivas <davanum@gmail.com>
96ecba2
to
6150378
Compare
@ehashman whoops. thanks. done. |
/retest |
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.
re-
/lgtm
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Cheef5, dims, mrunalp 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 |
/retest Review the full test history for this PR. Silence the bot with an |
marking Dockershim only flags as deprecated.
Signed-off-by: Davanum Srinivas davanum@gmail.com
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Which issue(s) this PR fixes:
Related to kubernetes/enhancements#2221
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: