No checks to verify critical steps

[lxie123]

While running through this workshop, I noticed that users can skip certain critical steps and still move to the next section. They may only find out much later that the end result will not work.

For example, if they skips the step to push the image to the repo. they won't know that there is problem until it's time to test the app. May be very difficult for new users to troubleshoot this.

It may be useful to make sure to confirm these critical steps are done before students can move forward. This is a " nice to have".

[eitansuez]

does the katacoda scenario handle this issue?
my sense is that for this simple hands-on course, we should assume users can figure out why some command might return an error. pretty much every educates workshop out there behaves like this.
e.g. if someone doesn't apply their deployment on step n, some subsequent command on step n+m will likely produce an error too.

[lxie123]

I think this one is a little more obscure , like you wont find it till many steps down the line.. Maybe after steps like this we can actually run another command to verify it was pushed.. Like curl repo command...

Other labs do that too.. like kubectl apply -f and then follow up with kubectl get ...

Also we want to raise the bar, not do what every other workshop does right ? :)

[eitansuez]

fyi..the point of this specific workshop was to be a 1-to-1 port of the existing katacoda scenario, nothing more. partly, it was to find out if we could use eduk8s to achieve the same thing that the existing katacoda scenario did.