mirror of https://github.com/easzlab/kubeasz.git
add issue template
gjmzj
parent
84760323d6
commit
4138a9ab4c
|
|
@ -0,0 +1,82 @@
|
||||||
|
name: Bug Report 问题提交
|
||||||
|
description: Report a bug encountered while using kubeasz 项目使用问题提交
|
||||||
|
labels: kind/bug
|
||||||
|
body:
|
||||||
|
- type: textarea
|
||||||
|
id: problem
|
||||||
|
attributes:
|
||||||
|
label: What happened? 发生了什么问题？
|
||||||
|
description: |
|
||||||
|
Please provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner.
|
||||||
|
操作命令，输出日志等，请尽可能提供详细信息，否则可能导致您的问题无法及时得到跟踪和解决。
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
|
||||||
|
- type: textarea
|
||||||
|
id: expected
|
||||||
|
attributes:
|
||||||
|
label: What did you expect to happen? 期望的结果是什么？
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
|
||||||
|
- type: textarea
|
||||||
|
id: repro
|
||||||
|
attributes:
|
||||||
|
label: How can we reproduce it (as minimally and precisely as possible)? 尽可能最小化、精确地描述如何复现问题
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
|
||||||
|
- type: textarea
|
||||||
|
id: additional
|
||||||
|
attributes:
|
||||||
|
label: Anything else we need to know? 其他需要说明的情况
|
||||||
|
|
||||||
|
- type: textarea
|
||||||
|
id: kubeVersion
|
||||||
|
attributes:
|
||||||
|
label: Kubernetes version k8s 版本
|
||||||
|
value: |
|
||||||
|
<details>
|
||||||
|
|
||||||
|
</details>
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
|
||||||
|
- type: textarea
|
||||||
|
id: kubeaszVersion
|
||||||
|
attributes:
|
||||||
|
label: Kubeasz version
|
||||||
|
value: |
|
||||||
|
<details>
|
||||||
|
|
||||||
|
</details>
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
|
||||||
|
- type: textarea
|
||||||
|
id: osVersion
|
||||||
|
attributes:
|
||||||
|
label: OS version 操作系统版本
|
||||||
|
value: |
|
||||||
|
<details>
|
||||||
|
|
||||||
|
```console
|
||||||
|
# On Linux:
|
||||||
|
$ cat /etc/os-release
|
||||||
|
# paste output here
|
||||||
|
$ uname -a
|
||||||
|
# paste output here
|
||||||
|
```
|
||||||
|
|
||||||
|
</details>
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
|
||||||
|
- type: textarea
|
||||||
|
id: plugins
|
||||||
|
attributes:
|
||||||
|
label: Related plugins (CNI, CSI, ...) and versions (if applicable) 其他网络插件等需要说明的情况
|
||||||
|
value: |
|
||||||
|
<details>
|
||||||
|
|
||||||
|
</details>
|
||||||
|
|
@ -0,0 +1,20 @@
|
||||||
|
name: Enhancement Tracking Issue
|
||||||
|
description: Provide supporting details for a feature in development
|
||||||
|
labels: kind/feature
|
||||||
|
body:
|
||||||
|
- type: textarea
|
||||||
|
id: feature
|
||||||
|
attributes:
|
||||||
|
label: What would you like to be added?
|
||||||
|
description: |
|
||||||
|
Feature requests are unlikely to make progress as issues.
|
||||||
|
A proposal that works through the design along with the implications of the change can be opened as a KEP.
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
|
||||||
|
- type: textarea
|
||||||
|
id: rationale
|
||||||
|
attributes:
|
||||||
|
label: Why is this needed?
|
||||||
|
validations:
|
||||||
|
required: true
|
||||||
|
|
@ -0,0 +1,57 @@
|
||||||
|
<!-- Thanks for sending a pull request! Here are some tips for you:
|
||||||
|
|
||||||
|
-->
|
||||||
|
|
||||||
|
#### What type of PR is this?
|
||||||
|
|
||||||
|
<!--
|
||||||
|
Add one of the following kinds:
|
||||||
|
/kind bug
|
||||||
|
/kind cleanup
|
||||||
|
/kind documentation
|
||||||
|
/kind feature
|
||||||
|
-->
|
||||||
|
|
||||||
|
#### What this PR does / why we need it:
|
||||||
|
|
||||||
|
#### Which issue(s) this PR fixes:
|
||||||
|
<!--
|
||||||
|
*Automatically closes linked issue when PR is merged.
|
||||||
|
Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`.
|
||||||
|
_If PR is about `failing-tests or flakes`, please post the related issues/tests in a comment and do not use `Fixes`_*
|
||||||
|
-->
|
||||||
|
Fixes #
|
||||||
|
|
||||||
|
#### Special notes for your reviewer:
|
||||||
|
|
||||||
|
#### Does this PR introduce a user-facing change?
|
||||||
|
<!--
|
||||||
|
If no, just write "NONE" in the release-note block below.
|
||||||
|
If yes, a release note is required:
|
||||||
|
Enter your extended release note in the block below. If the PR requires additional action from users switching to the new release, include the string "action required".
|
||||||
|
|
||||||
|
-->
|
||||||
|
```release-note
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
#### Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
|
||||||
|
|
||||||
|
<!--
|
||||||
|
This section can be blank if this pull request does not require a release note.
|
||||||
|
|
||||||
|
When adding links which point to resources within git repositories, like
|
||||||
|
KEPs or supporting documentation, please reference a specific commit and avoid
|
||||||
|
linking directly to the master branch. This ensures that links reference a
|
||||||
|
specific point in time, rather than a document that may change over time.
|
||||||
|
|
||||||
|
See here for guidance on getting permanent links to files: https://help.github.com/en/articles/getting-permanent-links-to-files
|
||||||
|
|
||||||
|
Please use the following format for linking documentation:
|
||||||
|
- [KEP]: <link>
|
||||||
|
- [Usage]: <link>
|
||||||
|
- [Other doc]: <link>
|
||||||
|
-->
|
||||||
|
```docs
|
||||||
|
|
||||||
|
```
|
||||||
Loading…
Reference in New Issue