Fix: secret missing in docker-registry secret command in kubectl-comm…

[MeenuyD]

Corrected the usage section for the 'kubectl create docker-registry' command to accurately reflect the command syntax.

Original:
$ kubectl create docker-registry NAME --docker-username=user --docker-password=password --docker-email=email [--docker-server=string] [--from-file=[key=]source] [--dry-run=server|client|none]

Corrected:
$ kubectl create secret docker-registry NAME --docker-username=user --docker-password=password --docker-email=email [--docker-server=string] [--from-file=[key=]source] [--dry-run=server|client|none]
#43180

[netlify]

✅ Pull request preview available for checking

Built without sensitive environment variables

Name	Link
🔨 Latest commit	da06ff0
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-io-main-staging/deploys/6510553fba66f00008fffb79
😎 Deploy Preview	https://deploy-preview-43185--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[dipesh-rawat]

Thank you for your contribution! The file (kubectl-commands.html) edited is generated automatically, not altered manually. For additional information, please refer to the following webpage: https://kubernetes.io/docs/contribute/generate-ref-docs/kubectl/

If this is an issue, we should fix either the generator code or the source the generator uses as its input. I'm not entirely familiar with the specifics of the generative logic. Perhaps @tengqm can provide feedback.

[dipesh-rawat]

For review and feedback.
/cc @tengqm

[MeenuyD]

Thank you for your contribution! The file (kubectl-commands.html) edited is generated automatically, not altered manually. For additional information, please refer to the following webpage: https://kubernetes.io/docs/contribute/generate-ref-docs/kubectl/

If this is an issue, we should fix either the generator code or the source the generator uses as its input. I'm not entirely familiar with the specifics of the generative logic. Perhaps @tengqm can provide feedback.

Thank you for the clarification! I appreciate the information about the generation process for the documentation.Thanks again for your guidance!

[Shubham82]

@MeenuyD For more information please refer to the description of the following PR #42664

[tengqm]

/lgtm
/approve
As a workaround.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: tengqm

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:

• OWNERS [tengqm]

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

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 64c80f11a01417a93eab5f39874b44df81391c06