Website: Issue with k8s.io/docs/tutorials/kubernetes-basics/deploy-app/deploy-interactive/

Created on 23 Nov 2019 · 11Comments · Source: kubernetes/website

This is a Bug Report

Problem:
Misleading explanation in the text compared to the command stated in the command line box. The test says to use the command kubectl run, but the command in the command line box uses kubectl create deployment

Proposed Solution:
Align the explanation in the text with the command to be executed.

Page to Update:
https://kubernetes.io/...

good first issue help wanted kinbug lifecyclstale prioritimportant-longterm

Source

andreaskring

All 11 comments

Thanks! I must have missed this when updating the example.

Alternatively, you can raise a PR at https://github.com/katacoda-scenarios/kubernetes-bootcamp-scenarios

BenHall on 23 Nov 2019

/kind bug
/priority important-longterm

sftim on 23 Nov 2019

Think it's appropriate to flag this as a
/good-first-issue

Mention me (@sftim) if you are looking at this and are not sure where to start.

sftim on 23 Nov 2019

@sftim:
This request has been marked as suitable for new contributors.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

Think it's appropriate to flag this as a
/good-first-issue

Mention me (@sftim) if you are looking at this and are not sure where to start.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

k8s-ci-robot on 23 Nov 2019

/assign

amalts on 25 Nov 2019

PR katacoda-scenarios/kubernetes-bootcamp-scenarios#16 will fix this.
@BenHall @sftim Please review.

amalts on 25 Nov 2019

👍1

@amalts Sorry for the delay, I didn't see the notification until now. This has been merged.

BenHall on 2 Dec 2019

👍1

/close

amalts on 5 Dec 2019

@amalts: You can't close an active issue/PR unless you authored it or you are a collaborator.

In response to this:

/close

k8s-ci-robot on 5 Dec 2019

Thanks @BenHall.
This can be closed @andreaskring

amalts on 5 Dec 2019

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale