Issue in kubectl-commands.html file

[alfein]

Hello team.

Recently I noticed that this page: https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands#-em-secret-tls-em- shows wrong command. Instead of

kubectl create tls NAME --cert=path/to/cert/file --key=path/to/key/file [--dry-run=server|client|none]

it should be

kubectl create secret tls NAME --cert=path/to/cert/file --key=path/to/key/file [--dry-run=server|client|none]

I believe the fix should go into this file https://github.com/kubernetes/website/blob/9ba644e361972562c5f3d39b92dedc8128c439b2/static/docs/reference/generated/kubectl/kubectl-commands.html

Please review.

Thank you

[nitishfy]

/assign

[jihoon-seo]

• kubectl create secret
  • kubectl create docker-registry -> kubectl create secret docker-registry
  • kubectl create generic -> kubectl create secret generic
  • kubectl create tls -> kubectl create secret tls
• kubectl create service
  • kubectl create clusterip -> kubectl create service clusterip
  • kubectl create externalname -> kubectl create service externalname
  • kubectl create loadbalancer -> kubectl create service loadbalancer
  • kubectl create nodeport -> kubectl create service nodeport

Also see this:

#35586 (comment)

This file (website/static/docs/reference/generated/kubectl/kubectl-commands.html) is auto-generated, please don't fix it here.

#35586 (comment)

FWIW, the upstream source code is here:
https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/kubectl/pkg/cmd/create/create_secret_tls.go#L93

[dipankardas011]

@jihoon-seo should this issue and its corresponding PR be closed?

[jihoon-seo]

@dipankardas011
@nitishkumar06 closed his prior PR, and opened another one in k/k.

IMO it would be good to keep this issue open until the error in K8s Docs has been resolved. 😊

/kind bug

[dipankardas011]

@dipankardas011
@nitishkumar06 closed his prior PR, and opened another one in k/k.

IMO it would be good to keep this issue open until the error in K8s Docs has been resolved. 😊

/kind bug

Okay 👍

[mehabhalodiya]

/triage accepted

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[nitishfy]

@jihoon-seo Should the PR be opened in Kuberenetes/website?

[vaibhav2107]

/remove-lifecycle stale