Mirror/k3s
1
0
Fork 0
mirror of https://github.com/k3s-io/k3s.git synced 2024-06-07 19:41:36 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update bug_report template

Browse Source
This commit is contained in:
David Nuzik 2020-05-06 16:51:37 -07:00
parent f38082673d
commit 6c32700616
1 changed files with 16 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
.github/ISSUE_TEMPLATE/bug_report.md vendored
View File

@ -7,25 +7,30 @@ assignees: ''
---
<!-- Thanks for helping us to improve k3s! We welcome all bug reports. Please fill out each area of the template so we can better help you. ***You can delete this message portion of the bug report.*** -->
<!-- Thanks for helping us to improve K3s! We welcome all bug reports. Please fill out each area of the template so we can better help you. Comments like this will be hidden when you post but you can delete them if you wish. -->
**Version:**
<!-- Provide the output from `k3s -v` -->
**Environmental Info:**
K3s Version:
<!-- Provide the output from "k3s -v" -->
**K3s arguments:**
<!-- Provide the flags used to install or run k3s server. -->
Node(s) CPU architecture, OS, and Version:
<!-- Provide the output from "uname -a" on the node(s) -->
**Describe the bug**
Cluster Configuration:
<!-- Provide some basic information on the cluster configuration. For example, "3 masters, 2 workers". -->
**Describe the bug:**
<!-- A clear and concise description of what the bug is. -->
**To Reproduce**
<!-- Steps to reproduce the behavior: -->
**Steps To Reproduce:**
<!-- Steps to reproduce the behavior. Please include as the first step how you installed K3s on the node(s) (including all flags or environment variables). If you have customized configuration via systemd drop-ins or overrides (https://coreos.com/os/docs/latest/using-systemd-drop-in-units.html) please include those as well. -->
- Installed K3s:
**Expected behavior**
**Expected behavior:**
<!-- A clear and concise description of what you expected to happen. -->
**Actual behavior**
**Actual behavior:**
<!-- A clear and concise description of what actually happened. -->
**Additional context / logs**
**Additional context / logs:**
<!-- Add any other context and/or logs about the problem here. -->