fix: todo resource request in workshop should be scheduled to the worker cluster

SaphMB commented 3 weeks ago

In the Writing your first Promise section of the workshop, the learner is told to verify that their todo app request has been deployed to the the worker cluster with:

kubectl --context $WORKER get deployments

However, the app has no selectors to ensure that is is deployed on the worker cluster and can end up on the platform cluster.

Acceptance Given a user has followed the instructions in Writing your first Promise When they apply the app Promise Then the resource is consistently scheduled to the worker cluster

kirederik commented 2 weeks ago

do we know what's the context behind this issue? Where they running it locally or via Instruqt? Was this reported by a single user or many?

It feels user error as it should never happen if you follow the instructions in order.

The platform cluster is scheduled with strictMatchLabels: true and the label environment=platform
This snippet of code should block Kratix from considering the Platform destination (since the above is true)

Did some testing on instruqt and could not reproduce

SaphMB commented 2 weeks ago

@kirederik Interesting, they were doing the workshop on Instruqt and reported observing that the the app could be scheduled to the platform. Two people mentioned this

syntasso / kratix-docs

fix: todo resource request in workshop should be scheduled to the worker cluster #146