-
Notifications
You must be signed in to change notification settings - Fork 5.2k
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
Update docs for cri-tools #2191
Conversation
/cc @yujuhong @Random-Liu |
cc @kubernetes/sig-node-pr-reviews |
/assign @Random-Liu @yujuhong |
contributors/devel/cri-validation.md
Outdated
|
||
- By setting flags `--runtime-endpoint` and `--image-endpoint` | ||
- By setting environment variables `CRI_RUNTIME_ENDPOINT` and `CRI_IMAGE_ENDPOINT` | ||
critest connects to `unit:///var/run/dockershim.sock` by default. For other runtimes, the endpoint can be set by flags `-runtime-endpoint` and `-image-endpoint`. |
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.
s/unit/unix
Is it -runtime-endpoint
or --runtime-endpoint
?
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.
ACK, those options are Go flags, so -runtime-endpoint
is right. Also additional flags are in same format.
critest connects to `/var/run/dockershim.sock` by default. For other runtimes, the endpoint can be set in two ways: | ||
|
||
- By setting flags `--runtime-endpoint` and `--image-endpoint` | ||
- By setting environment variables `CRI_RUNTIME_ENDPOINT` and `CRI_IMAGE_ENDPOINT` |
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.
Were the environment variables removed, and why?
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.
Yep, those environment variables are introduced with lib github.com/urfave/cli
. But with this lib, critest requires Go installed whenever running validation tests. So we moved to go test -c
for building critest binary and it doesn't require Go for running critest.
@yujuhong Addressed comments. PTAL |
/lgtm |
@cblecker Could you help to approve the PR? |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cblecker 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 |
Documentation for kubernetes/enhancements#292.