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
[WIP] Initial-cut of cri-dockerd #74051
[WIP] Initial-cut of cri-dockerd #74051
Conversation
37e7831
to
2260087
Compare
ad9a566
to
187bb62
Compare
187bb62
to
a35ad5c
Compare
a35ad5c
to
5302f0a
Compare
62d51c0
to
c5d02aa
Compare
c5d02aa
to
3a73103
Compare
@dims: Closed this PR. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
3a73103
to
20d4620
Compare
e31bafc
to
b926ec1
Compare
/test pull-kubernetes-integration |
/test pull-kubernetes-local-e2e-containerized |
d22b23e
to
902b5ac
Compare
902b5ac
to
0b69d25
Compare
- Stripped down code from cmd/kubelet - Remove the functionality that moved to cri-dockerd binary - add import-restrictions to monitor changes to dependencies - added myself to OWNERS for cri-dockerd Change-Id: I0dbc4109266cf8d66dca08c68e490fa930628c2c
Change-Id: I1ebeae40c7cf541fe802954da5c93d4463c7b110
0b69d25
to
7ce1f74
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: dims The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/retest |
// so we do all our parsing manually in Run, below. | ||
// DisableFlagParsing=true provides the full set of flags passed to the cri-dockerd in the | ||
// `args` arg to Run, without Cobra's interference. | ||
DisableFlagParsing: true, |
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.
Is this still required? Does cri-dockerd
need KubeletConfiguration
to operate or it needs only the docker shim related command line flags of the kubelet?
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.
@rosti until we move cri-dockerd
into its own repo, it seemed best to keep this stuff the same between "regular" kubelet and "cri-dockerd" in terms of command line flags and config parsing.
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 need to figure out how to tell the users to install the new cri-dockerd
binary.
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.
@dims Indeed, I can see that this outside the scope of this PR, but we can still add a simplification TODO there.
The complex way of doing command line parsing in the kubelet is required, because of the ability to override config fields with command line flags. If we don't need the KubeletConfiguration in cri-dockerd, then we can greatly simplify things.
@neolit123 that can be done by adding a dependency in the kubelet package to the cri-dockerd package.
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 the kubelet with dockershim and cri-dockerd have to be supported in parallel for a while.
first cri-dockerd has to become a part of the node packages and the kubernetes release process and only once the first classed deployers like kops, kubeadm etc switch to it we can remove dockershim.
i have concerns making the hard switch within one release as it may bust existing setups.
"dir": "/usr/bin", | ||
}, | ||
{ | ||
"files": ["cri-dockerd.service"], |
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 don't see this file in the PR. Perhaps it's missing or uncommitted?
Anyway, I presume it's going to be roughly equivalent to kubelet's systemd service 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.
Hmm, i missed this, will add one
@dims: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
/assign @rosti @neolit123 |
What type of PR is this?
/kind feature
What this PR does / why we need it:
We have a long standing TODO to break up kubelet's built-in docker shim into a separate binary. This brings docker in line with all the other CRI providers and levels the playing field for all CRI(s).
Which issue(s) this PR fixes:
Fixes #73933
Special notes for your reviewer:
Does this PR introduce a user-facing change?: