One artifact seems to be missing (recommendationservice 0.3.6) in gcr.io about microservices-demo HOT 4 CLOSED

Hi @djazayeri!

1. Repushed images recommendationservice:v0.3.6
Unfortunately, we don't have audit logs around Container Registry write operations to know why that image was deleted.
My guess is that it was removed (either automatically or manually) due to vulnerability count.
I've rebuilt and repushed the image. You should be unblocked now.
Fortunately, the vulnerability count of this particular image should be lower than before (IDK what the old vuln. count was), since today's rebuild used a newer version of python:3.7-slim.

2. Avoid using v0.3.6 and other old versions
v0.3.6 is a very old version of Online Boutique.
Question: Could you share a link to the piece of content that's using v0.3.6?
We should work towards updating the images and YAML manifests to the latest version.
Unfortunately, we only have automated tests for whatever's on main — and we don't make any promises about old versions of Online Boutique.

Sorry for the inconvenience.
Hope this helps. Thanks!

In case you're facing cache-related issues with the v0.3.6 image on your existing Kubernetes cluster, you can also try using the gcr.io/google-samples/microservices-demo/recommendationservice:v0.3.6-issue2367.

from microservices-demo.

I was following https://cloud.google.com/service-mesh/docs/onlineboutique-install-kpt. I will ask to get that updated to use the latest microservices-demo.

(Offhand do you know if there's anything non-trivial in updating those docs to use the latest?)

from microservices-demo.

Thanks for sharing the source (the Deploying the Online Boutique sample application tutorial).

Offhand do you know if there's anything non-trivial in updating those docs to use the latest?

Good question.

1. I believe the main differences between this repo's default Online Boutique deployment and anthos-service-mesh-packages's Online Boutique deployment are as follows:

   • anthos-service-mesh-packages deploys each microservice into its own namespace; while this repo deploys all microservices to the default namespace.
   • anthos-service-mesh-packages creates and assigns each microservice its own ServiceAccount while this repo uses the default ServiceAccount for all microservices (unless you explicitly opt into the this repo's ServiceAccount Kustomize Component)
   • anthos-service-mesh-packages doesn't deploy a Redis cache for the cartservice to use as a "database"

2. Between 0.3.6 and 0.9.0, the YAML definitions for the Deployment resources changed (to keep up with current versions of GKE/Kubernetes).

I'm happy to create the pull-request to update Online Boutique at https://github.com/GoogleCloudPlatform/anthos-service-mesh-packages.

from microservices-demo.

Pull-request to update that tutorial to use v0.9.0: GoogleCloudPlatform/anthos-service-mesh-packages#1575

from microservices-demo.