The installation instructions include references to community maintained artifacts for the Bookinfo sample application, which references community containers. The YAML configuration is located in the upstream Istio community Github repo, while some reference containers hosted on Dockerhub, which are prone to Docker's rate limit errors.

Users have encountered such rate limit errors when onboarding with OSSM, and this has the potential to interfere with customers onboarding with OSSM. It is also possible that customers use these steps as part of their own testing. Thus, this is a relatively high priority bug. By Red Hat's policies, we also should not be telling customers to install community artifacts. They also should not be hard coded to a particular Istio version (It looks like the links reference Istio 1.23, when OSSM is on 1.24).

Known instances:

Step 6 (apply bookinfo app yaml): https://docs.redhat.com/en/documentation/red_hat_openshift_service_mesh/3.0.0tp1/html/installing/ossm-installing-service-mesh#deploying-book-info_ossm-about-bookinfo-application

Step 2 (apply bookinfo gateway yaml):https://docs.redhat.com/en/documentation/red_hat_openshift_service_mesh/3.0.0tp1/html/installing/ossm-installing-service-mesh#ossm-accessing-bookinfo-application-using-istio-gateway-injection_ossm-about-accessing-bookinfo-application-using-gateway

Step 2 (apply bookinfo gateway api yaml):https://docs.redhat.com/en/documentation/red_hat_openshift_service_mesh/3.0.0tp1/html/installing/ossm-installing-service-mesh#ossm-accessing-bookinfo-application-using-gateway-api

Step 6 (deploy bookinfo app): https://docs.redhat.com/en/documentation/red_hat_openshift_service_mesh/3.0.0tp1/html/observability/distributed-tracing-and-service-mesh#ossm-config-otel_ossm-traces-assembly

Before passing this issue can be passed to docs, engineering should provide the updated commands that use a Red Hat maintained instance of bookinfo.

If there are other instances of community bookinfo, they should also be corrected.