Closed dewijones92 closed 1 year ago
Hi, can you check the logs of the controller
in knative-serving
and also post the yamls of the Knative resources for your service?
See https://knative.dev/docs/install/troubleshooting/#check-the-status-of-the-knative-resources and https://knative.dev/docs/install/troubleshooting/#check-the-status-of-the-knative-resources.
@ReToCode i have found the problem. Looks like the docker image does not exist in the registry?
Status:
Conditions:
Last Transition Time: 2023-05-25T06:30:23Z
Message: Revision "autoscale-go-00001" failed with message: Unable to fetch image "gcr.io/knative-samples/autoscale-go:0.1": failed to resolve image to digest: HEAD https://gcr.io/v2/knative-samples/autoscale-go/manifests/0.1: unexpected status code 404 Not Found (HEAD responses have no body, use GET for details).
Reason: RevisionFailed
Status: False
Type: ConfigurationsReady
Last Transition Time: 2023-05-25T06:30:23Z
chat gpt4 answer:
Based on the provided information, it appears that there is an issue with fetching the image for the "autoscale-go" revision in Knative. The error message states that the image "gcr.io/knative-samples/autoscale-go:0.1" cannot be resolved to a digest. Additionally, it mentions that when attempting to access the image manifest at "https://gcr.io/v2/knative-samples/autoscale-go/manifests/0.1," a 404 Not Found error is encountered.
To fix this issue, you can try the following steps:
Verify the image URL: Double-check that the image URL "gcr.io/knative-samples/autoscale-go:0.1" is correct. Make sure the image exists in the specified location.
Check image availability: Ensure that the image repository allows access and that the image is publicly available or that you have the necessary credentials to access it.
You are right. That sample is outdated, as we migrated stuff to the github registry. You can use
docker pull ghcr.io/knative/autoscale-go:latest
I'm going to fix the sample.
Hello 😊
I am trying to follow this https://knative.dev/docs/serving/autoscaling/autoscale-go/#prerequisites
But I am having no luck. I am stuck with this. Please help 😊
Expected Behavior
Service should deloy
Actual Behavior
Steps to Reproduce the Problem
kube details: https://gist.github.com/dewijones92/7525cd49775441c77b214ba1a6cacdc0
kube logs: https://gist.github.com/dewijones92/b9442115781dd48ae992e3c6124b109a
Many thanks 😊