Configure Renovate

[gardener-ci-robot]

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

---

Detected Package Files

• Dockerfile (dockerfile)
• .github/workflows/publish-docs.yml (github-actions)
• go.mod (gomod)
• charts/druid/requirements.yaml (helm-requirements)
• charts/druid/values.yaml (helm-values)

What to Expect

With your current configuration, Renovate will create 13 Pull Requests:

Update github.com/gardener/etcd-backup-restore digest to 43959b3

• Schedule: ["at any time"]
• Branch name: renovate/github.com-gardener-etcd-backup-restore-digest
• Merge into: master
• Upgrade github.com/gardener/etcd-backup-restore to 43959b3047a6aefbeaa092455f7b92739fd2e310

Update golang.org/x/exp digest to 7588d65

• Schedule: ["at any time"]
• Branch name: renovate/golang.org-x-exp-digest
• Merge into: master
• Upgrade golang.org/x/exp to 7588d65b2ba8

Update sigs.k8s.io/controller-runtime/tools/setup-envtest digest to 711b48b

• Schedule: ["at any time"]
• Branch name: renovate/sigs.k8s.io-controller-runtime-tools-setup-envtest-digest
• Merge into: master
• Upgrade sigs.k8s.io/controller-runtime/tools/setup-envtest to 711b48bccf1f

Update module github.com/ironcore-dev/vgopath to v0.1.7

• Schedule: ["at any time"]
• Branch name: renovate/github.com-ironcore-dev-vgopath-0.x
• Merge into: master
• Upgrade github.com/ironcore-dev/vgopath to v0.1.7

Update module github.com/onsi/ginkgo/v2 to v2.22.2

• Schedule: ["at any time"]
• Branch name: renovate/github.com-onsi-ginkgo-v2-2.x
• Merge into: master
• Upgrade github.com/onsi/ginkgo/v2 to v2.22.2

Update module github.com/onsi/gomega to v1.36.2

• Schedule: ["at any time"]
• Branch name: renovate/github.com-onsi-gomega-1.x
• Merge into: master
• Upgrade github.com/onsi/gomega to v1.36.2

Update module k8s.io/api to v0.32.0

• Schedule: ["at any time"]
• Branch name: renovate/k8s.io-api-0.x
• Merge into: master
• Upgrade k8s.io/api to v0.32.0

Update module k8s.io/apimachinery to v0.32.0

• Schedule: ["at any time"]
• Branch name: renovate/k8s.io-apimachinery-0.x
• Merge into: master
• Upgrade k8s.io/apimachinery to v0.32.0

Update module k8s.io/apiserver to v0.32.0

• Schedule: ["at any time"]
• Branch name: renovate/k8s.io-apiserver-0.x
• Merge into: master
• Upgrade k8s.io/apiserver to v0.32.0

Update module k8s.io/client-go to v0.32.0

• Schedule: ["at any time"]
• Branch name: renovate/k8s.io-client-go-0.x
• Merge into: master
• Upgrade k8s.io/client-go to v0.32.0

Update module k8s.io/component-base to v0.32.0

• Schedule: ["at any time"]
• Branch name: renovate/k8s.io-component-base-0.x
• Merge into: master
• Upgrade k8s.io/component-base to v0.32.0

Update module sigs.k8s.io/controller-tools to v0.17.0

• Schedule: ["at any time"]
• Branch name: renovate/sigs.k8s.io-controller-tools-0.x
• Merge into: master
• Upgrade sigs.k8s.io/controller-tools to v0.17.0

Update module gopkg.in/yaml.v2 to v3

• Schedule: ["at any time"]
• Branch name: renovate/gopkg.in-yaml.v2-3.x
• Merge into: master
• Upgrade gopkg.in/yaml.v2 to v3.0.1

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prhourlylimit for details.

---

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.

---

This PR has been generated by Renovate Bot.

[gardener-robot]

@gardener-ci-robot Thank you for your contribution.

[oliver-goetz]

hey folks 👋

we deployed renovate in our prow cluster and activated it for the repositories where prow is already running 🏡

renovate is an alternative to dependabot which is more flexible in regards of its configuration. You can use it if you like by configuring it using this PR or adding a config file by your own according to the docs.
There are also some hints in ci-infra repository you can check and there is a working configuration too.

If you don't like to use it, just close this PR (but do not rename it) and the 🤖 won't bother you again.

[shreyas-s-rao]

@oliver-goetz thanks. I like that renovate considers even image tags and golang versions for updates, which is quite convenient. But once renovate is enabled, can we still disable it by removing the renovate.json file, if we don't like it, maybe in terms of interactions on the PRs it raises?

[oliver-goetz]

yes, you can deactivate it again by deleting the config file 👍
Btw. I recommend to use a renovate.json5 file as we do in gardener/gardener. Its main advantage is that you are able to create comments there.

[shreyas-s-rao]

Thanks for the suggestion @oliver-goetz . Will take inspiration from the g/g renovate configuration too.

[seshachalam-yv]

/retest