Use better dependabot config like cluster-api-provider-packet uses

[cprivitere]

For comparison:

• https://github.com/kubernetes-sigs/cloud-provider-equinix-metal/blob/main/.github/dependabot.yml
• https://github.com/kubernetes-sigs/cluster-api-provider-packet/blob/main/.github/dependabot.yml

🤖 ChatGPT summary of differences (added by @displague)

---

The two Dependabot configurations you provided are similar in structure, but there are some notable differences:

1. Update Frequency:

   • In the CPEM configuration, updates are scheduled daily for all ecosystems (GitHub Actions, Go modules, and Docker images).
   • In the CAPP configuration, updates are scheduled weekly for GitHub Actions, Go modules, and Docker images. Additionally, the second configuration specifies specific days for Go module updates (Monday) and e2e test Go modules (Tuesday).

2. Commit Message Prefix:

   • Both configurations include a commit message prefix (:seedling:) for all ecosystems, indicating the nature of the update.

3. Labels:

   • The CAPP configuration includes labels for GitHub Actions and Docker updates (area/ci, ok-to-test for GitHub Actions, and ok-to-test for Docker). The labels provide additional context or categorization for the pull requests.

4. Grouping Dependencies:

   • The CAPP configuration includes a grouping mechanism for Go modules. Dependencies with a k8s.io prefix are grouped into a single pull request. This can help manage updates for related dependencies more efficiently.

5. Ignoring Specific Dependencies:

   • The CAPP configuration includes a section to ignore specific dependencies during updates. For Go modules, certain dependencies like controller-runtime, k8s.io/*, go.etcd.io/*, and others are excluded from automatic updates based on specific update types (semver-major, semver-minor).

6. Different Directories for Go Modules:

   • The CAPP configuration specifies different directories for maintaining e2e test Go modules (/test/e2e). This allows for more granular control over updates in specific parts of the codebase.

In summary, the CAPP configuration provides more fine-grained control over the update process, with specific days for updates, labels for categorization, and exclusion of certain dependencies from automatic updates. The grouping mechanism for Go modules and the ability to specify different directories for updates add flexibility in managing dependencies.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[cprivitere]

/triage accepted

[cprivitere]

/remove-lifecycle stale