serving icon indicating copy to clipboard operation
serving copied to clipboard

failed to resolve image to digest on knative istio-1.5.0 serving-1.4.0 and k8s-1.22

Open infonaresh opened this issue 3 years ago • 4 comments

Hi Team,

I am facing issue after upgrading my Azure k8s version from 1.21.9 to 1.22.6, previously it was working fine with 1.21.9 and Knative was- v0.23. That old knative version was not supported for my new aks k8s version(1.22.6). that way we have decided to upgrade knative services also.

Now it's started giving error while pulling api- service images from private azure acr registry .

error: Message: Revision "api-Servicename-00001" failed with message: Unable to fetch image "azure-repo-name.azurecr.io/xxx/api-Servicename:0.7.3-t0.7.3-test.71": failed to resolve image to digest: Get "https://azure-repo-name.azurecr.io/v2/": context deadline exceeded.

Steps to Reproduce the Problem

K8s version from 1.21.9 to 1.22.6 and Knative: from v0.23.0 to Istio file 1.5.0 and serving 1.4.0

Can you please help us to fix this issue

infonaresh avatar Jul 08 '22 09:07 infonaresh

Do you have more details on how you're setting up the secret to pull the image?

dprotaso avatar Jul 14 '22 16:07 dprotaso

And any details on how you setup a private registry etc.

dprotaso avatar Jul 14 '22 16:07 dprotaso

/triage needs-user-input

dprotaso avatar Jul 14 '22 16:07 dprotaso

@infonaresh do you have any more info?

dprotaso avatar Aug 18 '22 19:08 dprotaso

This issue is stale because it has been open for 90 days with no activity. It will automatically close after 30 more days of inactivity. Reopen the issue with /reopen. Mark the issue as fresh by adding the comment /remove-lifecycle stale.

github-actions[bot] avatar Nov 17 '22 01:11 github-actions[bot]

This issue or pull request is stale because it has been open for 90 days with no activity.

This bot triages issues and PRs according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, the issue is closed

You can:

  • Mark this issue or PR as fresh with /remove-lifecycle rotten
  • Close this issue or PR with /close

/lifecycle stale

knative-prow-robot avatar Dec 17 '22 01:12 knative-prow-robot