Issue

I am totally inexperienced with kubernetes at this point. I followed the getting started instructions and read through part of the concepts and tasks documentation before trying the tutorials.
In the hello-node tutorial a note mentions

If you installed Minikube locally, run minikube start.
hinting that one can follow the tutorial(s) locally. This worked fine for kubernetes basics module 1 and 2 and broke in module 3.

The init of module 3 runs

kubectl run kubernetes-bootcamp --image=gcr.io/google-samples/kubernetes-bootcamp:v1 --port=8080

which bind the containers 8080 port and makes it exposable through the proxy.

The kubectl run command is not shown in the previous 2 modules which use instead:

kubectl create kubernetes-bootcamp --image=gcr.io/google-samples/kubernetes-bootcamp:v1 

Unfortunately running kubctl create with this image does not expose port 8080 on the container, thus users following on a local minikube install get a 502 error trying to access the app through the proxy because the container cannot be reached.

For users curious enough to make it to this repo, manually running the kubctl run ... command locally yields the following warning:

kubectl run kubernetes-bootcamp --image=gcr.io/google-samples/kubernetes-bootcamp:v1 --port=8080        [1]
kubectl run --generator=deployment/apps.v1 is DEPRECATED and will be removed in a future version. Use kubectl run --generator=run-pod/v1 or kubectl create instead.
deployment.apps/kubernetes-bootcamp created

No option to set the port seems to exist for kubectl create

I am now confused as to how I can avoid the deprecation warning and still get operational containers (though additional research leads to declarative yaml descriptor files which haven't been broached in the tutorials though they were extensively mentionned in the concepts documentation)

Environment information

>cat /etc/lsb-release                                                                                       
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=19.10
DISTRIB_CODENAME=eoan
DISTRIB_DESCRIPTION="Ubuntu 19.10"
> kubectl version                                                                                       
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.3", GitCommit:"06ad960bfd03b39c8310aaf92d1e7c12ce618213", GitTreeState:"clean", BuildDate:"2020-02-12T13:43:46Z", GoVersion:"go1.13.7", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.2", GitCommit:"59603c6e503c87169aea6106f57b9f242f64df89", GitTreeState:"clean", BuildDate:"2020-01-18T23:22:30Z", GoVersion:"go1.13.5", Compiler:"gc", Platform:"linux/amd64"}
> minikube version                                                                                           
minikube version: v1.7.2
commit: 50d543b5fcb0e1c0d7c27b1398a9a9790df09dfb

It seems like there is no license information available for the exercises in this repo. Could somebody clarify this?

Description

In any Katacoda scenario, clicking a command with {{execute T2}} where T2 (or any extra terminal instance) doesn't yet exist doesn't actually run the command. It just opens the new terminal. You have to click the command again to execute it.

Examples of affected scenarios:

• https://katacoda.com/scenario-examples/scenarios/markdown-extensions (Section: Execute in Different Terminal Windows)
• https://kubernetes.io/docs/tutorials/kubernetes-basics/deploy-app/deploy-interactive/ (Step 3 of 3)

Steps to reproduce

1. Open a Katacoda scenario with a command that is configured to execute in a different terminal (example, T2).
2. Ensure that there are no terminals already open.
3. Run the command.

Expected outcome

The new terminal opens and the command executes.

Actual outcome

The new terminal opens but remains blank. Clicking the command a second time runs the command.

Debug information

Content Version: a0a7c76a698e3989610117d60940328ce8aa24ca

Last Updated: 2021-08-16T22:04:42.326Z

Connected - Katacoda Host: jago01 in us

host0 IP: 172.17.0.12
client1 IP: 172.17.0.38
host2 IP: 172.17.0.22
client3 IP: 172.17.0.44

When katacoda playground is opened, the server fails to upload the playground, and seems to be hanged.