-
Notifications
You must be signed in to change notification settings - Fork 40k
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
build: fix README instructions to load the output image tar #125674
Conversation
Hi @flavianmissi. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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-sigs/prow repository. |
/ok-to-test |
/sig release |
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
thank you!!
LGTM label has been added. Git tree hash: cdf9e9de3c4adeae6d3cab918e6eeff1975742aa
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BenTheElder, flavianmissi, saschagrunert 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 |
/triage accepted |
Docs only change, cc @kubernetes/release-team |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
Ran into an issue when following the build docs and trying to run a custom build of kube-controller-manager on my kind cluster. Found it reported here: #118231 (comment). The comment states we need to use
docker load
instead ofdocker import
, which I confirmed works as expected.This changes the docs so they reflect this.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: