Its great to see the Bootcamp walk me through the commands to the degree that I am almost feeling no friction at all. But at the same time, that is not a great thing either because I may not have learn about the commands and interaction at the end of the bootcamp. I propose you keep how things are but also introduce a way for user to encounter friction (user typing the commands himself). And then at the end of each module may be you can tell him e.g, how many commands he typed etc.

...until you get to the second page, where you see

  > block of code                                                                                         
bash: block: command not found                                                                            

  > block of code                                                                                         
bash: block: command not found                                                                            

  > block of code                                                                                         
bash: block: command not found                                                                            

  > block of code                                                                                         
bash: block: command not found       

When starting an interactive tutorial, the first few commands could encounter errors.

  > kubectl version                                                                                                        
bash: /home/scrapbook/.bin/kubectl: Permission denied                                                                      

  > kubectl version                                                                                                        
bash: /home/scrapbook/.bin/kubectl: Permission denied                                                                      

  > kubectl version                                                                                                        
bash: /home/scrapbook/.bin/kubectl: Permission denied                                                                      

  > kubectl version                                                                                                        
bash: /home/scrapbook/.bin/kubectl: Permission denied                                                                      

  > kubectl version                                                                                                        
Client Version: version.Info{Major:"1", Minor:"3", GitVersion:"v1.3.0", GitCommit:"283137936a498aed572ee22af6774b6fb6e9fd94
", GitTreeState:"clean", BuildDate:"2016-07-01T19:26:38Z", GoVersion:"go1.6.2", Compiler:"gc", Platform:"linux/amd64"}     
Server Version: version.Info{Major:"1", Minor:"3", GitVersion:"v1.3.3", GitCommit:"c6411395e09da356c608896d3d9725acab821418
", GitTreeState:"clean", BuildDate:"1970-01-01T00:00:00Z", GoVersion:"go1.6.2", Compiler:"gc", Platform:"linux/amd64"} 

I think it takes a while for the binaries to be copied and permissions to be changed.

  > ls -lh /home/scrapbook/.bin/                                                                                           
total 38M                                                                                                                  
-rwxr-xr-x 2 scrapbook scrapbook 7.6M Jul 29 16:17 docker-compose                                                          
-rw-r--r-- 1 scrapbook scrapbook  31M Aug 10 16:37 kubectl                                                                 
-rwxr-xr-x 1 scrapbook scrapbook 1.7K Aug 10 16:37 minikube                                                                

  > ls -lh /home/scrapbook/.bin/                                                                                           
total 62M                                                                                                                  
-rw-r--r-- 1 scrapbook scrapbook   75 Aug 10 16:37 aget_path                                                               
-rwxr-xr-x 2 scrapbook scrapbook 7.6M Jul 29 16:17 docker-compose                                                          
-rwxr-xr-x 1 scrapbook scrapbook  226 Aug 10 16:37 get_path                                                                
-rwxr--r-- 1 scrapbook scrapbook  54M Aug 10 16:37 kubectl                                                                 
-rwxr-xr-x 1 scrapbook scrapbook 1.7K Aug 10 16:37 minikube   

It'd be nice if the the prompt only appears after the setup is ready.

It just cycles back to the first question.

In this page https://kubernetesbootcamp.github.io/kubernetes-bootcamp/2-1.html, need to replace "[url to github repo]" with a real url link.

This diagram of node here https://kubernetesbootcamp.github.io/kubernetes-bootcamp/3-1.html leaves some doubt about whether there is one docker or multiple in the node. You have shows Docker next to kubelet thereby causing some confusion.

There seems to be a minor typo in the text of Q3 of the last quiz - quotes in random places.

The text "Is" at the start of the question should probably be changed to "The traffic is" e.g. "The traffic is dropped" not just "Is dropped".

Screens like https://containersolutions.github.io/kubernetes-bootcamp/2-0.html have a lot of vertical whitespace which forces me to scroll down for no real value

• The whole block, but particularly the text "Welcome" feels too big to me - the balance on later screens is much better
• It need not say 'jocatalin'
• block of code isn't in the same style as on later screens

I never realised the diagrams were slides that could be clicked through. I wonder if this could be made clearer somehow? It could well be my fault for skim-reading though.

Cloud shell hangs in the services section when I scrolled up and then down

I don't like how the new terminal is opened after kubectl proxy is run. I think this should be explained up front, instead of an after-the-fact note at the bottom.

As per the email sent to kubernetes-dev[1], please create a SECURITY_CONTACTS
file.

The template for the file can be found in the kubernetes-template repository[2].
A description for the file is in the steering-committee docs[3], you might need
to search that page for "Security Contacts".

Please feel free to ping me on the PR when you make it, otherwise I will see when
you close this issue. :)

Thanks so much, let me know if you have any questions.

(This issue was generated from a tool, apologies for any weirdness.)

[1] https://groups.google.com/forum/#!topic/kubernetes-dev/codeiIoQ6QE
[2] https://github.com/kubernetes/kubernetes-template-project/blob/master/SECURITY_CONTACTS
[3] https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance-template-short.md

Type a bunch of text:

Resize the window to be smaller than the text and the right part of the text will be cut off (bug 1):

Type some more in the terminal and the text will reflow, this time causing the text to overflow the right-hand side (bug 2):

Resize the window to be larger again and the right side will again be cut off (bug 1 again):

Type some more and the text will reflow but with a phantom line of characters that don't actually exist, but are duplicated from previous characters (bug 3):

Continue typing and eventually all the ghost characters will be overwritten:

Trying to do the steps in the tiny katakoda terminal is really difficult. You should be able to collapse the left nav to get a larger terminal.

https://kubernetesbootcamp.github.io/kubernetes-bootcamp/1-2.html tries to load https://katacoda.com/embed.js and fails. If you go to http://katacode.com you will see that domain expired.

As a side note, this repository doesn't really have a link to kubernetesbootcamp.github.io, and that site doesn't have a link back to this repository.

This project has been archived.
This project has been merged into the central Kubernetes docs repository.

This is the exact reason https://github.com/kubernetes-retired exists. Should we move this to kubernetes-retired/kubernetes-bootcamp?

We should just hide these

1. Browse to
2. Scroll down to the text
   RESULT: No link to actually read the bootcamp content
   EXPECT: Link to the index of the bootcamp content

Clicking the curl command is pasting the previous export command instead.

"A group of one or more application containers that include shared volume and IP address"

I think this should read "... that share an IP address and volumes" or similar.

--image=docker.io/jocatalin/kubernetes-bootcamp:v1

This could be hosted on gcr.io, and again not reference jocatalin.

When I took the quiz and was asked to leave us a comment. In the pop up it says "Sample Question" and that title doesn't seem appropriate. (Screenshot attached) - kubernetes-bootcamp.png

https://containersolutions.github.io/kubernetes-bootcamp/2-2.html

When I click "kubectl run kubernetes-bootcamp --image=docker.io/jocatalin/kubernetes-bootcamp:v1 --port=8080" what gets pasted is "o/jocatalin/kubernetes-bootcamp:v1 --port=8080cker.i"

After completing a scenario in Katakoda, click the right arrow after "Step X of X" and you see a "Congratulations!" screen with a "Next Scenario" button. Clicking that button results in:

Coming Soon
Sorry, it looks like you've come across something not quite ready yet, bare with us.

to most UNIX heads, $ is the non-root prompt and # is the root prompt. The current terminal uses > which generally means a line-continuation in bash. I suggest changing > to $

All K8s subrepositories should have a CONTRIBUTING.md file, which at the minimum should point to https://github.com/kubernetes/community/blob/master/contributors/guide/README.md. Care should be taken that all information is in sync with the contributor guide.

Subrepositories may also have contributing guidelines specific to that repository. They should be explicitly documented and explained in the CONTRIBUTING.md

Ref: kubernetes/community#1832

It would be nice to be able to click the wrong answers after you have clicked the right one, just to read the blurb below.

First page:

We already installed minikube for you. Check that it is properly installed, by running the minikube version command:

minikube version ↵

Both of these are styled as if they should be clickable, but only the second one does anything.

It's quite jarring compared to the rest of the page. It looks like it is supposed to be using Roboto Slab but isn't for some reason.

Color the commands which can be clicked and executed, with a different color

Hey guys,

First of all, I love this demo and the way that it's set up. Just a quick intro into how everything works, in the browser, it's great :)

However, I did notice some odd things in the code here in the repository. First of all, the javascript code for the v2 application still returns v=1, according to the code (response.end(" | v=1\n");). However, the actual demo nicely returns v=2.

Additionally, and this is one I am less sure of due to my limited experience with Docker: in the Dockerfile, it says EXPOSE 8080, which I assume means make port 8080 available to requests from outside the container. However, in the v1 application (not v2, just v1), the server is started on 8081 (www.listen(8081,function () {).

Are these two just mismatches in the code, that have been fixed for the actual demo, or am I missing something here?

From @craigbox:

Also, after clicking this, I get a page where my only action is to click 'begin'. I would expect to be taken straight into the quiz.

When I maximize my window, the instruction text in katakoda gets huge.

The interactive tutorial will give error messages if you attempt to use it immediately since it downloads kubectl and other setup after providing the command prompt. Should probably not allow the user to do anything until it is fully setup.

You can type in the terminal, but it's not made obvious with the instructions, which just say 'click the blocks'. We could make it more obvious that it is possible to interact in any way you wish.

When you get to the second module, you're running kubectl proxy, and it says "open another terminal window" - it confused me for a second that you do that with the +, so perhaps a primer to the environment might be a good idea somewhere?

(Also, I can connect to things with nc, which you might not expect should be possible.)