Allow dependabot to check go modules

[jlosito]

What this PR does / why we need it:

This change allows dependabot to check go dependencies which this project uses on a weekly basis and submit pull requests with version bumps in order to keep packages up-to-date.

https://docs.github.com/en/github/administering-a-repository/keeping-your-actions-up-to-date-with-dependabot

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Which issue/s this PR fixes

How Has This Been Tested?

GitHub should already have a validator for these types of configuration files which is automatically ran in order to check the dependabot configuration is syntactically correct.

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I've read the CONTRIBUTION guide
• I have added tests to cover my changes.
• All new and existing tests passed.

[k8s-ci-robot]

Welcome @jlosito!

It looks like this is your first PR to kubernetes/ingress-nginx 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/ingress-nginx has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @jlosito. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[rikatz]

Using dependabot is pretty cool (I use on my personal projects), but I'm afraid that it can bring some problems, for example with the kubernetes libraries.

Usually before updating them, we try to make some tests. Is that possible to ignore some libraries in dependabot? If so, I think it would be good to configure this to at least ignore the k8s libraries, which are sort of the core of this controller.

[rikatz]

/ok-to-test

[jlosito]

If one wanted to ignore some packages, you can add something like the following.

---
version: 2
updates:
  - package-ecosystem: "gomod"
    directory: "/"
    schedule:
      interval: "weekly"
    ignore:
      - dependency-name: "k8s.io/api"

https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore

I'm pretty sure the bot provides some chatop commands to ignore a dependency and it will automatically update the configuration file accordingly.

[rikatz]

Can we instead of use Dependabot to open PRs of old libraries, use it to generate a report that can be sent on a weekly based to a webhook (like Slack)?

[rikatz]

/lgtm
/approve
It wont hurt to look dependabot working on our repo :) (but if it does, we can remove it!)

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jlosito, rikatz

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [rikatz]

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

[tao12345666333]

Keeping up to date is not bad