From d0a1c957f9b6f8e55cabc43be6f9ff366d487775 Mon Sep 17 00:00:00 2001 From: tonyxrmdavidson Date: Tue, 20 Aug 2024 13:48:49 +0100 Subject: [PATCH] Creating Known Issues Section on README This commit will add a Known Issues section and also add information about a known image rate limiting issue which occasionally causes an ImagePullBackoff error Signed-off-by: tonyxrmdavidson Requested Changes from @isinyaaa accepted Co-authored-by: Isabella Basso Removing Unused Codeblock This commit removes the unused codeblock Signed-off-by: tonyxrmdavidson --- README.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/README.md b/README.md index 910857cd..131e04c1 100644 --- a/README.md +++ b/README.md @@ -132,3 +132,15 @@ End-to-end testing is developed with Robot Framework; this higher-lever layer of - demonstrate *User Stories* from high level perspective - demonstrate coherent logical data mapping by performing the same high level capabilities, using REST API flow Vs Python client flow, directly checking the end results in the backend gRPC MLMD server. + +## Known Issues +### Model-Registry-db mysql:8.3.0 rate limiting + +Ocassionally you may encounter an 'ImagePullBackOff' error within the model-registry-db container. See example below. + +``` +Failed to pull image “mysql:8.3.0”: rpc error: code = Unknown desc = fetching target platform image selected from image index: reading manifest sha256:f9097d95a4ba5451fff79f4110ea6d750ac17ca08840f1190a73320b84ca4c62 in docker.io/library/mysql: toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit +``` + +This error occurs when using the default mysql:8.3.0. You can instead try to pull the image from another registry by updating it on [manifests/kustomize/overlays/db/model-registry-db-deployment.yaml](./manifests/kustomize/overlays/db/model-registry-db-deployment.yaml): +spec.template.spec.containers.image: public.ecr.aws/docker/library/mysql:8.3.0