OSToy images are not multi-architecture

[davivcgarcia]

Description

The sample workloads used in the lab uses a container image built for amd64 only, making it unsuited for workshops exploring ROSA Machine Pools based on arm64 with AWS Graviton. Deploying the YAML in a cluster with mixed machine pools, the pods can be scheduled to the incompatible node.

Error

The pods related to backend and frontend deployments will be in CrashLoopbackOff status, and the logs would say something like this:

kubectl -n ostoy logs ostoy-microservice-6666dcf455-9fhvp
exec /usr/local/bin/docker-entrypoint.sh: exec format error

Suggest Fix

Update the Deployment resources to leverage nodeSelector for amd64 architctures.

 nodeSelector:
   kubernetes.io/arch: amd64