fix: reference missing files in schema (Closes #20752)

[zvdy]

Summary

Added the missing schemas to the map in order to fix #20752 , did not modify updateHashFile as the modified files are not binaries:

Testing

❯ go run ./update_cni_plugins_version.go
I0515 00:26:31.427559  559144 update.go:91] The Plan:
{
  ".github/workflows/master.yml": {
    "Content": null,
    "Replace": {
      "CNI_PLUGIN_VERSION=\\\"v[0-9.]+\\\"": "CNI_PLUGIN_VERSION=\\\"v9.9.9\\\""
    }
  },
  ".github/workflows/pr.yml": {
    "Content": null,
    "Replace": {
      "CNI_PLUGIN_VERSION=\\\"v[0-9.]+\\\"": "CNI_PLUGIN_VERSION=\\\"v9.9.9\\\""
    }
  },
  "deploy/iso/minikube-iso/arch/aarch64/package/cni-plugins-latest-aarch64/cni-plugins-latest.mk": {
    "Content": null,
    "Replace": {
      "CNI_PLUGINS_LATEST_AARCH64_VERSION = .*": "CNI_PLUGINS_LATEST_AARCH64_VERSION = v9.9.9"
    }
  },
  "deploy/iso/minikube-iso/arch/x86_64/package/cni-plugins-latest/cni-plugins-latest.mk": {
    "Content": null,
    "Replace": {
      "CNI_PLUGINS_LATEST_VERSION = .*": "CNI_PLUGINS_LATEST_VERSION = v9.9.9"
    }
  },
  "deploy/kicbase/Dockerfile": {
    "Content": null,
    "Replace": {
      "CNI_PLUGINS_LATEST_VERSION=.*": "CNI_PLUGINS_LATEST_VERSION=\"v9.9.9\""
    }
  },
  "hack/jenkins/installers/check_install_cni_plugins.sh": {
    "Content": null,
    "Replace": {
      "CNI_PLUGIN_VERSION=\\\"v[0-9.]+\\\"": "CNI_PLUGIN_VERSION=\\\"v9.9.9\\\""
    }
  }
}
I0515 00:26:31.428074  559144 update.go:99] Local repo successfully updated

These would be the files (version is changed as i had to hardcode data in order to run it locally )

❯ rg --hidden 'CNI_PLUGIN_VERSION' --glob '!*.md'
.github/workflows/master.yml
570:          CNI_PLUGIN_VERSION=\"v9.9.9\"
571:          CNI_PLUGIN_TAR="cni-plugins-linux-amd64-$CNI_PLUGIN_VERSION.tgz" # change arch if not on amd64
574:          curl -LO "https://github.com/containernetworking/plugins/releases/download/$CNI_PLUGIN_VERSION/$CNI_PLUGIN_TAR"

.github/workflows/pr.yml
568:          CNI_PLUGIN_VERSION=\"v9.9.9\"
569:          CNI_PLUGIN_TAR="cni-plugins-linux-amd64-$CNI_PLUGIN_VERSION.tgz" # change arch if not on amd64
572:          curl -LO "https://github.com/containernetworking/plugins/releases/download/$CNI_PLUGIN_VERSION/$CNI_PLUGIN_TAR"

hack/jenkins/installers/check_install_cni_plugins.sh
19:CNI_PLUGIN_VERSION=\"v9.9.9\"
20:CNI_PLUGIN_TAR="cni-plugins-linux-amd64-$CNI_PLUGIN_VERSION.tgz"
23:curl -qL -O "https://github.com/containernetworking/plugins/releases/download/$CNI_PLUGIN_VERSION/$CNI_PLUGIN_TAR"

cc: @medyagh

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: zvdy (e901f76, a32d4d4, e0a128d)

[k8s-ci-robot]

Welcome @zvdy!

It looks like this is your first PR to kubernetes/minikube 🎉. 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/minikube 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 @zvdy. 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-sigs/prow repository.

[k8s-ci-robot]

Keywords which can automatically close issues and at(@) or hashtag(#) mentions are not allowed in commit messages.

The list of commits with invalid commit messages:

• e901f76 fix: reference missing files in schema (Closes improve automation "update-cni-plugins-version" to update it everywhere #20752)

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-sigs/prow repository. I understand the commands that are listed here.

[k8s-ci-robot]

Keywords which can automatically close issues and at(@) mentions are not allowed in the title of a Pull Request.

You can edit the title by writing /retitle in a comment.

When GitHub merges a Pull Request, the title is included in the merge commit. To avoid invalid keywords in the merge commit, please edit the title of the PR.

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-sigs/prow repository. I understand the commands that are listed here.

[minikube-bot]

Can one of the admins verify this patch?

[zvdy]

Sorry for the duped commits, I lost the thread while going through the CLA

[medyagh]

excellent ! thank you @zvdy for the quick fix

[medyagh]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: medyagh, zvdy

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 [medyagh]

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