auto label issues depending on OS

[VannTen]

What would you like to be added

• Convert the OS field in the bug-report issue form to a dropdown input

  kubespray/.github/ISSUE_TEMPLATE/bug-report.yaml

  Lines 39 to 45 in 1f186ed

  	- type: textarea
  	id: os
  	attributes:
  	label: OS
  	placeholder: 'printf "$(uname -srm)\n$(cat /etc/os-release)\n"'
  	validations:
  	required: true

  
  => values should be based on

  kubespray/roles/kubernetes/preinstall/defaults/main.yml

  Lines 117 to 137 in 1f186ed

  	# Currently known os distributions
  	supported_os_distributions:
  	- 'RedHat'
  	- 'CentOS'
  	- 'Fedora'
  	- 'Ubuntu'
  	- 'Debian'
  	- 'Flatcar'
  	- 'Flatcar Container Linux by Kinvolk'
  	- 'Suse'
  	- 'openSUSE Leap'
  	- 'openSUSE Tumbleweed'
  	- 'ClearLinux'
  	- 'OracleLinux'
  	- 'AlmaLinux'
  	- 'Rocky'
  	- 'Amazon'
  	- 'Kylin Linux Advanced Server'
  	- 'UnionTech'
  	- 'UniontechOS'
  	- 'openEuler'

  I think ?
• Auto label issues by OS using https://github.com/marketplace/actions/advanced-issue-labeler
• I think this would also needs to add the relevant labels into kubernetes/test-infra (see Add CI labels for kubernetes-sigs/kubespray kubernetes/test-infra#33289 for an examples)

/help
/good-first-issue

Why is this needed

This could help us get data (in a aggregatable form) of the distribution of ours users regarding base OS.

ref : https://kubernetes.slack.com/archives/C13J86Z63/p1736424818419419?thread_ts=1736414039.059959&cid=C13J86Z63

[k8s-ci-robot]

@VannTen:
This request has been marked as suitable for new contributors.

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-good-first-issue command.

In response to this:

What would you like to be added

• Convert the OS field in the bug-report issue form to a dropdown input

  kubespray/.github/ISSUE_TEMPLATE/bug-report.yaml

  Lines 39 to 45 in 1f186ed

  	- type: textarea
  	id: os
  	attributes:
  	label: OS
  	placeholder: 'printf "$(uname -srm)\n$(cat /etc/os-release)\n"'
  	validations:
  	required: true

  
  => values should be based on

  kubespray/roles/kubernetes/preinstall/defaults/main.yml

  Lines 117 to 137 in 1f186ed

  	# Currently known os distributions
  	supported_os_distributions:
  	- 'RedHat'
  	- 'CentOS'
  	- 'Fedora'
  	- 'Ubuntu'
  	- 'Debian'
  	- 'Flatcar'
  	- 'Flatcar Container Linux by Kinvolk'
  	- 'Suse'
  	- 'openSUSE Leap'
  	- 'openSUSE Tumbleweed'
  	- 'ClearLinux'
  	- 'OracleLinux'
  	- 'AlmaLinux'
  	- 'Rocky'
  	- 'Amazon'
  	- 'Kylin Linux Advanced Server'
  	- 'UnionTech'
  	- 'UniontechOS'
  	- 'openEuler'

  I think ?
• Auto label issues by OS using https://github.com/marketplace/actions/advanced-issue-labeler
• I think this would also needs to add the relevant labels into kubernetes/test-infra (see Add CI labels for kubernetes-sigs/kubespray kubernetes/test-infra#33289 for an examples)

/help
/good-first-issue

Why is this needed

This could help us get data (in a aggregatable form) of the distribution of ours users regarding base OS.

ref : https://kubernetes.slack.com/archives/C13J86Z63/p1736424818419419?thread_ts=1736414039.059959&cid=C13J86Z63

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.

[aman4433]

/assign