Image Version updated to avoid image pullbackoff error.#3221
Open
ChinaBrahma wants to merge 12 commits intoGoogleCloudPlatform:mainfrom
Open
Image Version updated to avoid image pullbackoff error.#3221ChinaBrahma wants to merge 12 commits intoGoogleCloudPlatform:mainfrom
ChinaBrahma wants to merge 12 commits intoGoogleCloudPlatform:mainfrom
Conversation
|
Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). View this failed invocation of the CLA check for more information. For the most up to date status, view the checks section at the bottom of the pull request. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Background
Previously, the Kubernetes manifest files used short image names (e.g.,
image: adservice). This configuration causedImagePullBackOfferrors when deployed on a remote cluster (like AWS EC2) because Kubernetes defaulted to looking for these images on Docker Hub, where they do not exist. The manifests were missing the specific container registry URL.Fixes
Fixes
ImagePullBackOfferrors inkubernetes-manifests.Change Summary
Updated all microservice deployment manifests to use the official Google Container Registry (
gcr.io) paths and pinned them to versionv0.10.1to ensure stability.| Service Name | Correct Image URL |
| adservice |
gcr.io/google-samples/microservices-demo/adservice:v0.10.1|| cartservice |
gcr.io/google-samples/microservices-demo/cartservice:v0.10.1|| checkoutservice |
gcr.io/google-samples/microservices-demo/checkoutservice:v0.10.1|| currencyservice |
gcr.io/google-samples/microservices-demo/currencyservice:v0.10.1|| emailservice |
gcr.io/google-samples/microservices-demo/emailservice:v0.10.1|| frontend |
gcr.io/google-samples/microservices-demo/frontend:v0.10.1|| paymentservice |
gcr.io/google-samples/microservices-demo/paymentservice:v0.10.1|| productcatalog |
gcr.io/google-samples/microservices-demo/productcatalogservice:v0.10.1|| recommendation |
gcr.io/google-samples/microservices-demo/recommendationservice:v0.10.1|| shippingservice |
gcr.io/google-samples/microservices-demo/shippingservice:v0.10.1|Additional Notes
The
redisimage remains asredis:alpinebecause it is a standard image available on the public Docker Hub.Testing Procedure
Apply the updated manifests:
kubectl apply -f ./kubernetes-manifestsMonitor pod status:
kubectl get podsVerify that all pods transition from
ImagePullBackOfforPendingtoRunningstate.(Optional) Access the frontend via NodePort or LoadBalancer to confirm the application is live.
Related PRs or Issues
N/A