Add Auto-Labeling of Issues Based on OS Selection

[aman4433]

What type of PR is this?

/kind feature

What this PR does / why we need it:

This PR introduces an automatic labeling mechanism based on the operating system (OS) specified in bug reports.

The primary objective is to capture and label the user's OS when an issue is raised. This enables aggregation and analysis of user data, helping us better understand the distribution of OS usage among our users.

Which issue(s) this PR fixes:

Fixes #11873

Special notes for your reviewer:

The OS field in the bug-report issue form has been converted into a dropdown menu for consistency and ease of selection. The list of supported OS options has been sourced from Kubespray's preinstall defaults.

A GitHub Action workflow for advanced issue labeling has been introduced. This workflow auto-assigns an OS label based on the OS selected in the bug report.

The implementation leverages the Advanced Issue Labeler GitHub Action, as described in the #11873 issue.

Your review and feedback on the OS dropdown implementation and the GitHub Action integration would be greatly appreciated!

Does this PR introduce a user-facing change?:

NONE

[k8s-ci-robot]

Welcome @aman4433!

It looks like this is your first PR to kubernetes-sigs/kubespray 🎉. 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-sigs/kubespray 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 @aman4433. Thanks for your PR.

I'm waiting for a kubernetes-sigs 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.

[ant31]

/label ci-short

[ant31]

/ok-to-test

[VannTen]

Do we want to only supported OS in the choices array ? I wouldn't use this as a "List of supported OS", it's mainly to help us with categorization and stats. I don't have a strong opinion, though

[tico88612]

I don't know if it's possible to do something like Label with just the system (e.g., Ubuntu, Debian, etc.), but with system + version (e.g., Ubuntu 24.04, Debian 12, etc.) in the text.
Because this is a bug report, and I think it's strange that there's no version in the text.

[ant31]

Do we want to only supported OS in the choices array ? I wouldn't use this as a "List of supported OS", it's mainly to help us with categorization and stats. I don't have a strong opinion, though

Would help to have a label "supported OS" could help to focus time. Or with the OS label:

• Ubuntu 24.04 (supported)
• RHEL 8 (nop)

[VannTen]

Yes, but I'd say that better done in another PR, to keep this one simple.

[ant31]

can't it just be added in the OS label directly ?
Or you would prefer a separate label ?
https://github.com/kubernetes-sigs/kubespray/pull/11880/files#diff-fe9734cc5d2a0e1916553dbc343214eab5630814c0b0a27d1370c4569afaea67R43-R48

Anything to be done to enable github actions ?

[VannTen]

I'd rather have a separate label, since what's supported changes over time.

[aman4433]

Hi everyone,

I’ve made the requested changes and committed them. Let me know if you have any feedback or if there are any changes you’d like me to make.

Thanks in advance!

[VannTen]

/approve
/release-note-edit

NONE

Looks good enough for me, we can iterate on that.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aman4433, VannTen

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

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

[ant31]

/lgtm