mirror of
https://github.com/k3s-io/k3s.git
synced 2024-06-07 19:41:36 +00:00
36 lines
1.4 KiB
Markdown
36 lines
1.4 KiB
Markdown
---
|
|
name: Bug report
|
|
about: Create a report to help us improve
|
|
title: ''
|
|
labels: ''
|
|
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. Comments like this will be hidden when you post but you can delete them if you wish. -->
|
|
|
|
**Environmental Info:**
|
|
K3s Version:
|
|
<!-- Provide the output from "k3s -v" -->
|
|
|
|
Node(s) CPU architecture, OS, and Version:
|
|
<!-- Provide the output from "uname -a" on the node(s) -->
|
|
|
|
Cluster Configuration:
|
|
<!-- Provide some basic information on the cluster configuration. For example, "3 servers, 2 agents". -->
|
|
|
|
**Describe the bug:**
|
|
<!-- A clear and concise description of what the bug is. -->
|
|
|
|
**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:**
|
|
<!-- A clear and concise description of what you expected to happen. -->
|
|
|
|
**Actual behavior:**
|
|
<!-- A clear and concise description of what actually happened. -->
|
|
|
|
**Additional context / logs:**
|
|
<!-- Add any other context and/or logs about the problem here. --> |