-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
adding a new issue template for bug reports #258
Merged
+41
−0
Merged
Changes from 2 commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,38 @@ | ||
--- | ||
name: Bug report | ||
about: Create a report to help us improve | ||
title: '' | ||
labels: '' | ||
assignees: '' | ||
|
||
--- | ||
|
||
<!-- Thanks for helping us to improve K3K! 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:** | ||
Host Cluster Version: | ||
<!-- For example K3S v1.32.1+k3s1 or RKE2 v1.31.5+rke2r1 --> | ||
|
||
Node(s) CPU architecture, OS, and Version: | ||
<!-- Provide the output from "uname -a" on the node(s) --> | ||
|
||
Host Cluster Configuration: | ||
<!-- Provide some basic information on the cluster configuration. For example, "1 servers, 2 agents CNI: Flannel". --> | ||
|
||
K3K 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:** | ||
- Created a cluster with `k3k create`: | ||
|
||
**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. --> | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we add a hint on how to get the logs from k3k, I would say grabbing the k3k controller logs
and the k3k cluster logs, that includes server logs and in case of shared mode server logs plus k3k-kubelet logs