Website: k8s.io/docs/tutorials/kubernetes-basics/deploy-app/deploy-intro/ tutorial not consistent with linked source code

[optnfast]

This is a...

• [ ] Feature Request
• [x] Bug Report

Problem:

https://kubernetes.io/docs/tutorials/kubernetes-basics/deploy-app/deploy-intro/ says:

The source code and the Dockerfile are available in the GitHub repository for the Kubernetes Basics.

The server.js in github just responds "Hello World!" to any request. However the server in the interactive tutorial is more complex:

var handleRequest = function(request, response) {
  response.setHeader('Content-Type', 'text/plain');
  response.writeHead(200);
  response.write("Hello Kubernetes bootcamp! | Running on: ");
  response.write(host);
  response.end(" | v=1\n");
  console.log("Running On:" ,host, "| Total Requests:", ++requests,"| App Uptime:", (new Date() - startTime)/1000 , "seconds", "| Log Time:",new Date());
}

Particularly during module 3 step 2 this is very confusing - when the reader tries to match what they see in the terminal with what they have been told they are running, they will find they are not consistent. Only in step 4 does the reason for the discrepancy become apparent.

Proposed Solution:

Change the source code or the tutorial so that they match.

Page to Update:
https://kubernetes.io/docs/tutorials/kubernetes-basics/deploy-app/deploy-intro/

[ClaudiaJKang]

I think so. I opened same Issue(#8855) and PR(#8856).
But, PR wasn't reviewed yet.

[optnfast]

Looks like the assign to @BenHall didn't work, PR is still assigned to @zacharysarah .

[BenHall]

Thanks, it's a little confusing as the repo was originally stored elsewhere and merged in.

Let me see if I can untangle this in time for next weeks SIG-DOCS.

[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.

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

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

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.