fix: update digest lookup to use versioned RepoTags instead of latest

[shivakunv]

Biggest risk in config:
1, values.yaml and CSV are managed independently, so renovate can update one without keeping the other in sync.
2. Same tag, new digest, If the tag still exists, but upstream re-pushes that same tag to a different image, Renovate may keep the tag the same and only change the digest in csv file

Current Issue:
Renovate always pulls the digest from the latest tag, which results in a SHA difference.
However, the version in the values.yaml file is not updated in this scenario, so the digest in the manifests becomes mismatched and stale.

Solution:
Open a PR only when the RepoTags value in values.yaml changes.
Then search for that exact digest in
bundle/manifests/gpu-operator-certified.clusterserviceversion.yaml
instead of using the digest from latest.

check open PRs:
https://github.com/shivakunv/gpu-operator/pulls

[shivakunv]

PTAL @cdesiniotis @tariq1890

[coveralls]

coverage: 29.401%. remained the same — grouptagcommitwithbundle into main

[rajathagasthya]

This largely looks good to me. Just a couple of questions.

[shivakunv]

PTAL @tariq1890
Since @cdesiniotis has already confirmed that this image tagging convention will work, the renovate.json file will not impact our build process.

Regarding this section:

- name: vfio-manager-image
   image: ghcr.io/nvidia/k8s-driver-manager:0d30fa9c

I have only added TODO comments.

[cdesiniotis]

@shivakunv I took a look at some of the sample PRs raised in your fork, and I noticed that only one line gets updated in the bundle/manifests/gpu-operator-certified.clusterserviceversion.yaml (the CSV file). Note, that for each container image in the CSV file, there are two lines that need to be updated. For example, for dcgm-exporter, both this line and this line need to be updated. Can you confirm that renovate is updating both occurrences? Do you have an example PR that demonstrates this?

[shivakunv]

@shivakunv I took a look at some of the sample PRs raised in your fork, and I noticed that only one line gets updated in the bundle/manifests/gpu-operator-certified.clusterserviceversion.yaml (the CSV file). Note, that for each container image in the CSV file, there are two lines that need to be updated. For example, for dcgm-exporter, both this line and this line need to be updated. Can you confirm that renovate is updating both occurrences? Do you have an example PR that demonstrates this?

@cdesiniotis Thanks!!
I got carried away by too many changes and accidently removed a required change.
I have corrected it now and updated the code.

Please check my repo PRs opened by renovate:
https://github.com/shivakunv/gpu-operator-shiva/pulls

[cdesiniotis]

https://github.com/shivakunv/gpu-operator-shiva/pulls

I see two PRs raised today, https://github.com/shivakunv/gpu-operator-shiva/pull/233 and https://github.com/shivakunv/gpu-operator-shiva/pull/232. Both of these PRs only update the helm values, and not the CSV file.

[shivakunv]

https://github.com/shivakunv/gpu-operator-shiva/pulls

I see two PRs raised today, shivakunv/gpu-operator-shiva#233 and shivakunv/gpu-operator-shiva#232. Both of these PRs only update the helm values, and not the CSV file.

@cdesiniotis
Renovate properties show an older date if we had opened the same package PR earlier.
If you open these PR link (e.g. https://github.com/shivakunv/gpu-operator-shiva/pull/220), you will see that Renovate closes the existing PR and opens a new one.

Please check the snippets below for PR: https://github.com/shivakunv/gpu-operator-shiva/pull/220

[rahulait]

Other than few minor comments, the PR looks good to me.

[rahulait]

LGTM

[shivakunv]

opened PRs: https://github.com/shivakunv/gpu-operator/pulls