Website: Issue with /docs/tutorials/kubernetes-basics/expose-interactive/

[jverb]

This is a...

• [ ] Feature Request
• [x] Bug Report

Problem:
In Module 4 Step 1, the following two commands have the wrong name of the server:

kubectl describe services/kubernetes-bootcamp

export NODE_PORT=$(kubectl get services/kubernetes-bootcamp -o go-template='{{(index .spec.ports 0).nodePort}}')
echo NODE_PORT=$NODE_PORT

It should be kubernetes and not services/kubernetes-bootcamp. See the output of the get and describe command:

> kubectl get services/kubernetes
NAME         CLUSTER-IP   EXTERNAL-IP   PORT(S)   AGE
kubernetes   10.0.0.1     <none>        443/TCP   24m

  > kubectl describe services/kubernetes
Name:                   kubernetes
Namespace:              default
Labels:                 component=apiserver
                        provider=kubernetes
Selector:               <none>
Type:                   ClusterIP
IP:                     10.0.0.1
Port:                   https   443/TCP
Endpoints:              172.17.0.20:8443
Session Affinity:       ClientIP
No events.

Proposed Solution:
Change kubernetes-bootcamp to kubernetes

Page to Update:
https://kubernetes.io/docs/tutorials/kubernetes-basics/expose-interactive/

[alaczi]

I think that is ok, the problem is in the previous step, the expose deployment fails:

kubectl expose deployment/kubernetes-bootcamp --type="NodePort" --port 8080
Error from server (NotFound): deployments.extensions "kubernetes-bootcamp" not found

This is due that the environment is clean when you start the tutorial, you need to deploy it first to be able to expose it.

kubectl run kubernetes-bootcamp --image=docker.io/jocatalin/kubernetes-bootcamp:v1 --port=8080

[fejta-bot]

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.

Prevent issues from auto-closing with an /lifecycle frozen comment.

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

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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 rotten
/remove-lifecycle stale

[BenHall]

Thank you for the feedback. We've updated this to automatically deploy the previous state.

/close