add dependabot to image builder repo

[nawazkh]

Change description

• This PR adds dependabot to image-builder repo.

Related issues

Additional context

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign mboersma for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[nawazkh]

Not sure if I am missing any context on why dependabot was not added to this repo, so creating this PR to add it.

[nawazkh]

/cc @mboersma @jsturtevant @jackfrancis

[AverageMarcus]

There's some background context in this issue: #1283

Could you please include examples of what updates dependabot will generate for us? What versions will be covered, what wont?

[nawazkh]

Thank you for sharing the context @AverageMarcus. It is an interesting challenge to update various hardcoded semver-versions along with dependabot version updates.

I have an idea, not sure how viable, but here it is: (I will mark this PR draft to avoid notification churn)

• Configure dependabot to update versions in package-manager. In our case, say Dependabot updates a dependency in Dockerfile.
• Have a script that scans all the dirs for below files and find dependencies variables, replace them with latest version in the same Dependabot's PR(this can be achieved using GitHub actions).
  • *.json
  • .hcl
  • *.sh

Marking this PR WIP and push changes soon. Thanks!

[k8s-triage-robot]

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

This bot triages PRs 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 PR is closed

You can:

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

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

/lifecycle stale