Change:
This is a Feature Request <!-- Please only use this template for submitting feature/enhancement requests --<!-- See for guidance on writing an actionable issue description. --What would you like to be <!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --Move the page from the to the Why is this needed Multiple versions of the kubectl documentation exists which can be merged into the kubectl reference section in the Kubernetes upstream website. Part of Comments <!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/good-first-issue /language-en /help-wanted
This request has been marked as suitable for new contributors. Please ensure that the issue body includes answers to the following questions: Why are we solving this issue? To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points? Does this issue have zero to low barrier of entry? How can the assignee reach out to you for help? For more details on the requirements of such an issue, please see and ensure that they are met. If this request no longer meets these requirements, the label can be removed by commenting with the command. <detailsIn response to : This is a Feature Request <!-- See for guidance on writing an actionable issue description. --<!-- Describe as precisely as possible how this feature/enhancement should work from the user perspective. What should be changed, etc. --<!-- Any additional related comments that might help. Drawings/mockups would be extremely helpful (if required). --/language-en /help-wanted Instructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/triage accepted
The source code to move is inside
/assign
/sig docs
Hey and I created a PR for this issue. Please take a look.
would you be willing to file some similar issues? I would mark them with /help but not with /good-first-issue
Yes, I'll create the rest of the issues today.

Discussion:
<ins> --- title: "Introduction To Kubectl" content_type: concept weight: 1 --- Kubectl is the Kubernetes cli version of a swiss army knife, and can do many things. While this Book is focused on using Kubectl to declaratively manage Applications in Kubernetes, it also covers other Kubectl functions. ## Command Families Most Kubectl commands typically fall into one of a few categories: | Type                                   | Used For                   | Description                                        | |----------------------------------------|----------------------------|----------------------------------------------------| | Declarative Resource Management        | Deployment and Operations (e.g. GitOps)   | Declaratively manage Kubernetes Workloads using Resource Config     | | Imperative Resource Management         | Development Only           | Run commands to manage Kubernetes Workloads using Command Line arguments and flags | | Printing Workload State | Debugging  | Print information about Workloads | | Interacting with Containers | Debugging  | Exec, Attach, Cp, Logs | | Cluster Management | Cluster Ops | Drain and Cordon Nodes | ## Declarative Application Management The preferred approach for managing Resources is through declarative files called Resource Config used with the Kubectl *Apply* command. This command reads a local (or remote) file structure and modifies cluster state to reflect the declared intent. {{< alert color="success" title="Apply" >}} Apply is the preferred mechanism for managing Resources in a Kubernetes cluster. {{< /alert >}} ## Printing state about Workloads Users will need to view Workload state. - Printing summarize state and information about Resources - Printing complete state and information about Resources - Printing specific fields from Resources - Query Resources matching labels ## Debugging Workloads Kubectl supports debugging by providing commands for: - Printing Container logs - Printing cluster events - Exec or attaching to a Container - Copying files from Containers in the cluster to a user's filesystem ## Cluster Management On occasion, users may need to perform operations to the Nodes of cluster.  Kubectl supports commands to drain Workloads from a Node so that it can be decommission or debugged. ## Porcelain Users may find using Resource Config overly verbose for *Development* and prefer to work with the cluster *imperatively* with a shell-like workflow.  Kubectl offers porcelain commands for generating and modifying Resources. - Generating + creating Resources such as Deployments, StatefulSets, Services, ConfigMaps, etc - Setting fields on Resources - Editing (live) Resources in a text editor {{< alert color="warning" title="Porcelain For Dev Only" >}} Porcelain commands are time saving for experimenting with workloads in a dev cluster, but shouldn't be used for production. {{< /alert >}} </ins>