-
Notifications
You must be signed in to change notification settings - Fork 462
kubelet: enable crio #52
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
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: rphillips If they are not already assigned, you can assign the PR to them by writing The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
9d5fb58 to
39d072e
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.
- why is this file required?
- who uses this ?
- how will we configure it if we somebody needs to configure it for their internal registry ??
/cc @crawford
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.
The file is needed since crio gets installed with a default config which only includes the registry.access.redhat.com registry. docker.io needs to be added to the registry list to pull in defaulted docker images.
/cc @sjenning
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 this only affects images like openshift/origin-machine-config-operator:latest as this is not a fully qualified name, it should have been docker.io/openshift/origin-machine-config-operator:latest.
I rather have people use fully qualified names, than put this file on each machine... @crawford WDYT?
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.
@rphillips can you change this file to suggestion made in the installer here
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.
updated
|
@rphillips also can you run |
|
@abhinavdahiya regenerated |
|
/hold We may want to merge the cross-repo crio PR's all at once. |
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 mentioned in openshift/installer#234 (comment), can you remove these empty sections?
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.
updated
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.
Why did you need to set this? Did you hit an error without it, or is it just increasing robustness? What's the default value? How did you decide on 10m?
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.
default is 2m. probably doesn't need to be changed. i think the cri-o docs recommend this, but i don't think it is needed.
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.
default is 2m. probably doesn't need to be changed
I'm in favor of dropping it then. The fewer local opinions we need to maintain, the better :).
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.
Yeah, I took the runtime-request-timeout from this recommendation: https://github.com/kubernetes-sigs/cri-o/blob/master/kubernetes.md#preparing-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.
Let's keep the time out then, as it might be required when we pull hyberkube image on slower network.
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.
It DRY things up a bit to have a templates/_base/all/files/container-registries.yaml or some such which would be added to both masters and workers. But perhaps that is more than we want to bite off in this particular PR.
1927d5f to
fcae8cc
Compare
|
Updated the PR and removed the --runtime-request-timeout. The default --runtime-request-timeout enforces a 2 minute timeout on image pulls... We may want to bump it up for slower networks. |
|
/hold cancel |
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.
--cni-conf-dir, --cni-bin-dir, --network-pluging are no longer required as cri-o handles everything.
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.
Thanks. Removed those options.
fcae8cc to
114b898
Compare
|
/hold I was testing these changes yesterday, networking is not ready to be used with crio in installer yet. openshift/installer#235 (comment) |
As it is recommended by https://github.com/kubernetes-sigs/cri-o/blob/master/kubernetes.md#preparing-kubelet Let's set it to |
|
@abhinavdahiya I added support for a 10m timeout, and an environment variable and file to be able to overwrite the default |
|
I think all the feedback has been addressed. I've tested this an it works: can this get approved? |
|
This looks good to me. @abhinavdahiya, do you want to mark your requested-change resolved? |
|
|
|
@rphillips @sjenning $ cat templates/_base/master/files/etc-sysconfig-crio-network.yaml
filesystem: "root"
mode: 0644
path: "/etc/sysconfig/crio-network"
contents:
inline: |
CRIO_NETWORK_OPTIONS=--cni-config-dir=/etc/kubernetes/cni/net.d --cni-plugin-dir=/etc/kubernetes/cni/bin
$ cat templates/_base/worker/files/etc-sysconfig-crio-network.yaml
filesystem: "root"
mode: 0644
path: "/etc/sysconfig/crio-network"
contents:
inline: |
CRIO_NETWORK_OPTIONS=--cni-config-dir=/etc/kubernetes/cni/net.d --cni-plugin-dir=/etc/kubernetes/cni/bin
``
Also rebase to 2 commits, one with changes and one with generated test_data `go test ./pkg/controller/templates/.. -u` |
|
Closing in favor of #63 |
logging cleanup for bz debug, progressing debug
Enables crio for the kubelet container runtime.