ci(renovate): add markers for remaining tools (almost)

[erikgb]

This adds missing Renovate markers for almost all versions in the tools module. I have replaced Go package digests with pseudo-versions, as I find them more human-readable and simpler to reason about. Also added some comments here and there.

I have still not found a good way of picking up the envtest releases, for example: https://github.com/kubernetes-sigs/controller-tools/releases/tag/envtest-v1.34.0. We can probably configure a custom Renovate manager for it, based on the link to the YAML file with releases documented here.

Note: I have tested this with both cert-manager and trust-manager.

[erikgb]

@inteon, I think we need your valuable input on this one! 🙏

[hjoshi123]

I am thinking we might need data source templates for the envtest since they are packaged separately as tags/releases

[erikgb]

@hjoshi123 Did you read the description. We could use https://raw.githubusercontent.com/kubernetes-sigs/controller-tools/master/envtest-releases.yaml as input to Renovate, I think. And maybe https://docs.renovatebot.com/modules/manager/jsonata/.

Well, not exactly. ChatGPT suggests something like this might work:

{
  "customDatasources": {
    "envtest": {
      "defaultRegistryUrl": "https://raw.githubusercontent.com/kubernetes-sigs/controller-tools/master/envtest-releases.yaml",
      "format": "yaml"
    }
  },
  "regexManagers": [
    {
      "fileMatch": ["(^|/)Makefile$"],
      "matchStrings": [
        // Example: ENVTEST_K8S_VERSION=1.30.0
        "ENVTEST_K8S_VERSION=(?<currentValue>.+)\\n"
      ],
      "datasourceTemplate": "custom.envtest",
      "depNameTemplate": "kubernetes"
    }
  ]
}

[hjoshi123]

yup that's what I was thinking @erikgb. We use a customDataSource with the file use transformTemplates to transform and get the version and feed that to the customManagers. I could do raise a PR about what I am thinking (if you are ok with it) once this one gets merged

[erikgb]

You are welcome to contribute this in a follow-up PR, if you can.

[ThatsMrTalbot]

You can also try using extractVersion to get tags without a prefix for a given package, for example:

{
  "packageRules": [
    {
      "matchPackageNames": ["bar"],
      "extractVersion": "^release-(?<version>.*)$"
    }
  ]
}

[inteon]

Not sure this will work, will renovate update pseudo versions?
Do you have docs/ experiment or do you just want to try and see?

[erikgb]

I am pretty sure this will work. With the current configuration, the pseudo-version upgrades is configured to require dependency dashboard approval. See example here: cert-manager/cert-manager#7924.

[hjoshi123]

I feel this should be okay to merge now and then I can create a follow up PR for the env test with a customDataSource

[inteon]

/approve
/lgtm

[cert-manager-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: inteon

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [inteon]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment