docs: add note referencing kind load image-archive --help

[AnjaliMishra1st]

Adds a short note pointing users to the CLI help output for additional flags, as suggested in issue #4051.

[k8s-ci-robot]

Hi @AnjaliMishra1st. 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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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.

[AnjaliMishra1st]

Hi @BenTheElder and @aojea,
This is a small documentation update based on the guidance in issue #4051.
Whenever you have time, could you please review and trigger /ok-to-test?
Thanks!

[AnjaliMishra1st]

Hi @stmcginnis @BenTheElder @aojea,
I have applied the suggested fix.
Could you please take another look and add /ok-to-test and /lgtm when possible?
Thank you!

[AnjaliMishra1st]

Fixed the backticks and updated the formatting.
@stmcginnis @BenTheElder @aojea
Please review and add /ok-to-test and /lgtm when possible. Thanks!

[stmcginnis]

Sort of on the fence about documenting to use --help since that's sort of a common CLI thing that in general should be used everywhere. But doesn't harm anything, and this might give some users a breadcrumb to help figure out what to do if they get stuck.

/ok-to-test
/lgtm

[AnjaliMishra1st]

Hi @aojea, @BenTheElder,
This PR now has /lgtm and all tests have passed.
Could you please review and add /approve when you get time?
Thank you!

[BenTheElder]

Maybe instead we should document somewhere that kind help exists.

That recursively documents --help and using it for subcommands. I don't think we want to add an entry like this to the docs for every command.

[k8s-ci-robot]

New changes are detected. LGTM label has been removed.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: AnjaliMishra1st
Once this PR has been reviewed and has the lgtm label, please ask for approval from stmcginnis. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[AnjaliMishra1st]

Hi @BenTheElder,
I have updated the PR according to your suggestion and added a general help
section instead of referencing --help for the specific command.

Please take a look when convenient. Thank you!

[stmcginnis]

I do like this better than just referencing --help.

Now my concern is placement. It kind of feels like it is just dropped in the middle of a different context. I don't know the best place for it, but what do folks think about it being a subsection at the end of the Installation section? That sort of seems logical to me because that section is about getting started with the CLI itself, then the rest of the sections are about performing specific tasks with it.

[stmcginnis]

nit: extra line not needed, so remove this if you do another update.

[stmcginnis]

Same here. If you use a markdown linter, they typically only want one blank line between elements.