-
Notifications
You must be signed in to change notification settings - Fork 6.8k
Updated offline documentation #12684
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
base: master
Are you sure you want to change the base?
Updated offline documentation #12684
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: bbaassssiiee The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Hi @bbaassssiiee. Thanks for your PR. I'm waiting for a github.com 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. DetailsInstructions 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. |
tico88612
left a comment
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.
Quick look
4715c6c to
eb5335d
Compare
|
/ok-to-test |
eb5335d to
b4d14d9
Compare
e0f4943 to
68dffce
Compare
9b2dead to
1a74030
Compare
Signed-off-by: Bas Meijer <[email protected]>
1a74030 to
5f8354d
Compare
|
HI @ErikJiang Would you please help to review it. |
What type of PR is this?
What this PR does / why we need it:
This is an update to the offline documentation that explains using private registries with containerd 2 or 1.7. It also reduces the number of URLs with the suggestion to use the original domains as top-registries in the
files_repo.Which issue(s) this PR fixes:
Fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?: