Resolving Image Pull Errors and Prepending Issues in DataHub 1.0 Upgrade

ingestion
1

Original Slack Thread

<@U06TM7M40RK> for the datahub 1.0 upgrade, we use our own docker registry for images, however in the values.yaml file we have the global imageRegistry field that is mandatory and is preppending the image name with causes an image error pull in EKS

2

To address the issue of the global.imageRegistry field in the values.yaml file causing image pull errors in EKS, you can consider the following steps:

  1. Understand the global.imageRegistry Field: The global.imageRegistry field is used to specify a custom Docker registry for all images. This field prepends the specified registry to the image names, which can cause issues if the registry is not correctly set up or if the images are not available in the specified registry.

  2. Check Image Availability: Ensure that all the required DataHub images are available in your custom Docker registry. You can verify this by checking the image tags and names in your registry.

  3. Modify the values.yaml File: If the global.imageRegistry field is causing issues, you can try removing or commenting out this field in the values.yaml file. Instead, specify the full image path for each component individually. This approach allows you to have more control over the image paths and avoid the automatic prepending of the registry.

  4. Specify Full Image Paths: In the values.yaml file, specify the full image path for each DataHub component. For example:

    datahub-gms:
  image:
    repository: your-registry/datahub-gms
    tag: 1.0.0
datahub-frontend:
  image:
    repository: your-registry/datahub-frontend-react
    tag: 1.0.0

  5. Test the Configuration: After making these changes, deploy the updated Helm chart to your EKS cluster and verify that the images are being pulled correctly.

Would you like more detailed steps or further customization options?

Sources:

3

<@U06TM7M40RK> I got rid of the gloval.imageRegistry field but now I get the error Failed to apply default image tag as a / is preppended

4

The DataHub’s documentation I have ingested does not mention how to resolve the issue of a / being prepended to the image name after removing the global.imageRegistry field. You might want to check if there are any other fields or configurations in your values.yaml that could be affecting the image path, such as individual image repository settings or default image tags. If this doesn’t help, please reach out to the DataHub support team for further assistance. :+1: 0 button :-1: 0 button :light_bulb: Hint: Mention @runllm in the thread for followups.

5

By the way, I found these links that might be relevant to what you’re looking for. Let me know if this helps: - No Code Upgrade (In-Place Migration Guide)

6

Hi :slight_smile: ! Did this interaction resolve your issue or do you still require assistance ?

Please tag @ RunLLM if you still need further assistance !

Or tag @Datahub Community Support if you require a person to take a look :slight_smile:

Hope this helps ! ><