Remove deprecated sections from crictl doc

Author: Aaina26

content/en/docs/tasks/debug/debug-cluster/crictl.md

@@ -72,12 +72,6 @@ documentation](https://github.com/kubernetes-sigs/cri-tools/blob/master/docs/cri
 
 The following examples show some `crictl` commands and example output.
 
-{{< warning >}}
-If you use `crictl` to create pod sandboxes or containers on a running
-Kubernetes cluster, the Kubelet will eventually delete them. `crictl` is not a
-general purpose workflow tool, but a tool that is useful for debugging.
-{{< /warning >}}
-
 ### List pods
 
 List all pods:
@@ -241,136 +235,6 @@ The output is similar to this:
 10.240.0.96 - - [06/Jun/2018:02:45:51 +0000] "GET / HTTP/1.1" 200 612 "-" "curl/7.47.0" "-"
 ```
 
-### Run a pod sandbox
-
-Using `crictl` to run a pod sandbox is useful for debugging container runtimes.
-On a running Kubernetes cluster, the sandbox will eventually be stopped and
-deleted by the Kubelet.
-
-1. Create a JSON file like the following:
-
-   ```json
-   {
-     "metadata": {
-       "name": "nginx-sandbox",
-       "namespace": "default",
-       "attempt": 1,
-       "uid": "hdishd83djaidwnduwk28bcsb"
-     },
-     "log_directory": "/tmp",
-     "linux": {
-     }
-   }
-   ```
-
-2. Use the `crictl runp` command to apply the JSON and run the sandbox.
-
-   ```shell
-   crictl runp pod-config.json
-   ```
-
-   The ID of the sandbox is returned.
-
-### Create a container
-
-Using `crictl` to create a container is useful for debugging container runtimes.
-On a running Kubernetes cluster, the container will eventually be stopped and
-deleted by the Kubelet.
-
-1. Pull a busybox image
-
-   ```shell
-   crictl pull busybox
-   ```
-   ```none
-   Image is up to date for busybox@sha256:141c253bc4c3fd0a201d32dc1f493bcf3fff003b6df416dea4f41046e0f37d47
-   ```
-
-2. Create configs for the pod and the container:
-
-   **Pod config**:
-
-   ```json
-   {
-     "metadata": {
-       "name": "busybox-sandbox",
-       "namespace": "default",
-       "attempt": 1,
-       "uid": "aewi4aeThua7ooShohbo1phoj"
-     },
-     "log_directory": "/tmp",
-     "linux": {
-     }
-   }
-   ```
-
-   **Container config**:
-
-   ```json
-   {
-     "metadata": {
-       "name": "busybox"
-     },
-     "image":{
-       "image": "busybox"
-     },
-     "command": [
-       "top"
-     ],
-     "log_path":"busybox.log",
-     "linux": {
-     }
-   }
-   ```
-
-3. Create the container, passing the ID of the previously-created pod, the
-   container config file, and the pod config file. The ID of the container is
-   returned.
-
-   ```shell
-   crictl create f84dd361f8dc51518ed291fbadd6db537b0496536c1d2d6c05ff943ce8c9a54f container-config.json pod-config.json
-   ```
-
-4. List all containers and verify that the newly-created container has its
-   state set to `Created`.
-
-   ```shell
-   crictl ps -a
-   ```
-
-   The output is similar to this:
-      
-   ```
-   CONTAINER ID        IMAGE               CREATED             STATE               NAME                ATTEMPT
-   3e025dd50a72d       busybox             32 seconds ago      Created             busybox             0
-   ```
-
-### Start a container
-
-To start a container, pass its ID to `crictl start`:
-
-```shell
-crictl start 3e025dd50a72d956c4f14881fbb5b1080c9275674e95fb67f965f6478a957d60
-```
-
-The output is similar to this:
-
-```
-3e025dd50a72d956c4f14881fbb5b1080c9275674e95fb67f965f6478a957d60
-```
-
-Check the container has its state set to `Running`.
-
-```shell
-crictl ps
-```
-The output is similar to this:
-
-```
-CONTAINER ID   IMAGE    CREATED              STATE    NAME     ATTEMPT
-3e025dd50a72d  busybox  About a minute ago   Running  busybox  0
-```
-
 ## {{% heading "whatsnext" %}}
 
 * [Learn more about `crictl`](https://github.com/kubernetes-sigs/cri-tools).