krew-index not automatically updated on a new release

[VoyTechnology]

What happened:

New versions of the plugin are not automatically updated in the krew-index

What you expected to happen:

The pipeline located in .github/workflows/plugin.yaml should create a new PR in the krew-index using the krew-release-bot.

NGINX Ingress controller version (exec into the pod and run nginx-ingress-controller --version.): N/A

Kubernetes version (use kubectl version): N/A

Environment: N/A

How to reproduce this issue:

All tagged releases should create a new PR in https://github.com/kubernetes-sigs/krew-index/pulls. Without public output of Github Actions this has to be investigated by the maintainers, therefore I cannot provide any steps to reproduce the issue.

Anything else we need to know:

https://github.com/rajatjindal/krew-release-bot#limitations-of-krew-release-bot mentions that The first version of plugin has to be submitted manually, by plugin author, to the krew-index repo. Perhaps this was not originally done.

The functionality has been originally added in #8812 by @Volatus (mention for FYI purposes)

[k8s-ci-robot]

This issue is currently awaiting triage.

If Ingress contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

[longwuyuan]

/help

[k8s-ci-robot]

@longwuyuan:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

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.

[github-actions]

This is stale, but we won't close it automatically, just bare in mind the maintainers may be busy with other tasks and will reach your issue ASAP. If you have any question or request to prioritize this, please reach #ingress-nginx-dev on Kubernetes Slack.