How to resolve if Deployment Status shows Failed or Degraded when you pull images from private container registry

How to resolve if Deployment Status shows Failed or Degraded when you pull images from private container registry

If the deployment status shows Failed or Degraded, then the cluster is not able to pull container image from the private registry. In that case, the status of pod shows ImagePullBackOff.

The failure of deployment can be one of the following reasons:
  1. Provided credentials may not have permission to pull container image from registry.
  2. Provided credentials may be invalid.
You can resolve the ImagePullBackOff issue by clicking How to resolve? on the App Details page.
To provide the auto-inject credentials to the specific clusters for pulling the image from the private repository, click Manage Access which will take you to the Container Registries page.

  1. On the Container Registries page, select the docker registry and click Manage.
  2. In the Auto-inject credentials to clusters, click Confirm to edit to select the specific cluster or all clusters for which you want to auto-inject the credentials to and click Save.
  3. Redeploy the application after allowing the access.


    • Related Articles

    • [Resolved] Workaround for resolving npm warn tar TAR_BAD_ARCHIVE: Unrecognized archive format

      Overview Recently, users have encountered issues in their Node.js builds, reporting errors such as: npm WARN tar TAR_BAD_ARCHIVE: Unrecognized archive format Request failed "304 Not Modified" (if using Yarn as the package manager). This issue has ...

    • Getting UPGRADE FAILED: cannot patch "postgresql-postgresql" while upgrading Devtron to newer versions

      Debug: Make sure to annotate and label all the Devtron resources. Description of error Error: UPGRADE FAILED: cannot patch "postgresql-postgresql" with kind StatefulSet: StatefulSet.apps "postgresql-postgresql" is invalid: spec: Forbidden: updates to ...

    • Not able to see commits, throwing exit status 128

      1. Save the Git Repository Again Wait for few minutes and check the build pipeline if commits are visible or not 2. Check git sensor pod logs kubectl logs -n devtroncd -l app=git-sensor If you still get the same issue, try to bounce the pod and save ...

    • Devtron Enterprise DT-33 Release Note

      The latest release of Devtron is here, with new features and enhancements. Here's a summary of the DT-33 release and related updates. Highlights: Exception in Configuration Approval Policies (Beta) When urgent releases are needed, teams often face ...

    • Devtron Enterprise DT-34 Release Note

      The latest release of Devtron is here, with new features and enhancements. Here's a summary of the DT-34 release and related updates. Highlights: Support for Bulk Deployment of Only Active (Non-Hibernated) Apps While executing bulk deployments, users ...