Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update hello-minikube.md #39190

Merged
merged 2 commits into from
Feb 6, 2023
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 8 additions & 5 deletions content/en/docs/tutorials/hello-minikube.md
Original file line number Diff line number Diff line change
Expand Up @@ -90,14 +90,17 @@ tutorial has only one Container. A Kubernetes
Pod and restarts the Pod's Container if it terminates. Deployments are the
recommended way to manage the creation and scaling of Pods.

1. Use the `kubectl create` command to create a Deployment that manages a Pod. The
1. Katacoda environment only: At the top of the terminal pane, click the plus sign, and then click open a new terminal.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Isn't Katacoda shut down? Is there some other way to run Katacoda?

Copy link
Contributor Author

@Jun10ng Jun10ng Feb 2, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Katacoda is working still.
The following is what happened to me:
At the selection of create a deployment, user's terminal will be block on $ minikube dashboard, so we need reminder users to open a new terminal.

Did you mean we can run minikube dashboard with & ?


2. Use the `kubectl create` command to create a Deployment that manages a Pod. The
Jun10ng marked this conversation as resolved.
Show resolved Hide resolved
Pod runs a Container based on the provided Docker image.


```shell
kubectl create deployment hello-node --image=registry.k8s.io/e2e-test-images/agnhost:2.39 -- /agnhost netexec --http-port=8080
```

2. View the Deployment:
3. View the Deployment:

```shell
kubectl get deployments
Expand All @@ -110,7 +113,7 @@ Pod runs a Container based on the provided Docker image.
hello-node 1/1 1 1 1m
```

3. View the Pod:
4. View the Pod:

```shell
kubectl get pods
Expand All @@ -123,13 +126,13 @@ Pod runs a Container based on the provided Docker image.
hello-node-5f76cf6ccf-br9b5 1/1 Running 0 1m
```

4. View cluster events:
5. View cluster events:

```shell
kubectl get events
```

5. View the `kubectl` configuration:
6. View the `kubectl` configuration:

```shell
kubectl config view
Expand Down