Skip to content

Commit 57472c4

Browse files
authoredJan 31, 2025··
Update issue templates
1 parent 227315a commit 57472c4

File tree

2 files changed

+79
-16
lines changed

2 files changed

+79
-16
lines changed
 

‎.github/ISSUE_TEMPLATE/bug_report.md

+60-10
Original file line numberDiff line numberDiff line change
@@ -2,23 +2,73 @@
22
name: Bug report
33
about: Create a report to help us improve
44
title: ''
5-
labels: bug
5+
labels: ''
66
assignees: ''
77

88
---
99

10-
**Describe the bug**
11-
A concise description of what the bug is.
10+
<!--- ❤️ Thanks for taking the time to report this issue. Before you open an issue, please check if a similar issue [already exists](https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues) or has been closed before. If so, add additional helpful details to the existing issue to show that it's affecting multiple people. If not, to help us investigate, please provide the following information. ❤️-->
1211

13-
**Steps to reproduce**
12+
<!-- 🚨 IMPORTANT!!!
13+
Please complete at least the following sections
14+
- Bug Description
15+
- Steps to Reproduce
16+
- Expected Behavior
17+
- Environment
18+
Issue missing details will be closed, as they are crucial for understand the problem. 🚨 -->
1419

15-
**Expected outcome**
16-
A concise description of what you expected to happen.
20+
**Bug Description**
21+
<!--- A concise description of what the bug is -->
22+
23+
**Steps to Reproduce**
24+
<!--- Provide a step-by-step guide to reproduce the bug. If relevant, provide the controller logs with any error messages you are seeing and relevant Kubernetes Manifests.-->
25+
- Step-by-step guide to reproduce the bug:
26+
- Manifests applied while reproducing the issue:
27+
- Controller logs/error messages while reproducing the issue:
28+
29+
**Expected Behavior**
30+
<!--- Describe what you expected to happen instead of the observed behavior -->
31+
32+
**Actual Behavior**
33+
<!--- Describe what actually happens, including details on
34+
- whether the bug causes the controller to stop working entirely or impact some functionality
35+
- how often this bug occur ? [e.g., Always / Often / Occasionally / Rarely]
36+
-->
37+
38+
**Regression**
39+
Was the functionality working correctly in a previous version ? [Yes / No]
40+
If yes, specify the last version where it worked as expected
41+
42+
**Current Workarounds**
43+
<!--- If any workarounds exist, describe them here. If none exist, state "No workarounds available" -->
1744

1845
**Environment**
46+
- AWS Load Balancer controller version:
47+
- Kubernetes version:
48+
- Using EKS (yes/no), if so version?:
49+
- Using Service or Ingress:
50+
- AWS region:
51+
- How was the aws-load-balancer-controller installed:
52+
- If helm was used then please show output of `helm ls -A | grep -i aws-load-balancer-controller`
53+
- If helm was used then please show output of `helm -n <controllernamespace> get values <helmreleasename>`
54+
- If helm was not used, then copy/paste the exact command used to install the controller, including flags and options.
55+
- Current state of the Controller configuration:
56+
- `kubectl -n <controllernamespace> describe deployment aws-load-balancer-controller`
57+
- Current state of the Ingress/Service configuration:
58+
- `kubectl describe ingressclasses`
59+
- `kubectl -n <appnamespace> describe ingress <ingressname>`
60+
- `kubectl -n <appnamespace> describe svc <servicename>`
61+
62+
**Possible Solution (Optional)**
63+
<!--- If you have insights into the cause or potential fix, please share them. -->
1964

20-
* AWS Load Balancer controller version
21-
* Kubernetes version
22-
* Using EKS (yes/no), if so version?
65+
**Contribution Intention (Optional)**
66+
<!---If the solution is accepted, would you be willing to submit a PR?
67+
- if yes, please follow https://github.com/kubernetes-sigs/aws-load-balancer-controller/blob/main/CONTRIBUTING.md to start your contribution.
68+
- If you're not able to contribute a fix, the issue will be open for public contribution. High-impact issues will receive priority attention. We encourage community participation to help resolve issues faster.
69+
-->
70+
- [ ] Yes, I'm willing to submit a PR to fix this issue
71+
- [ ] No, I cannot work on a PR at this time
2372

24-
**Additional Context**:
73+
**Additional Context**
74+
<!---Add any other context about the problem here.-->

‎.github/ISSUE_TEMPLATE/feature_request.md

+19-6
Original file line numberDiff line numberDiff line change
@@ -2,16 +2,29 @@
22
name: Feature request
33
about: Suggest an idea for this project
44
title: ''
5-
labels: enhancement
5+
labels: ''
66
assignees: ''
77

88
---
99

10-
**Is your feature request related to a problem?**
11-
A description of what the problem is. For example: I'm frustrated when [...]
10+
<!--- ❤️ Thanks for taking the time to fill out this feature request report! We kindly ask that you search to see if a feature request [already exists](https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues?q=is%3Aissue%20state%3Aopen%20label%3Akind%2Ffeature) for your feature. If yes, show your support for features by up voting a discussion or by adding meaningful details which help the feature definition become more clear. If not, please provide following details to have the greatest chance of being worked on by a contributor. ❤️-->
1211

13-
**Describe the solution you'd like**
14-
A description of what you want to happen.
12+
**Describe the feature you are requesting**
13+
<!--- Provide a clear and concise description of the feature -->
14+
15+
**Motivation**
16+
<!--- Provide context about how it will benefit users or improve the project overall. -->
17+
18+
**Describe the proposed solution you'd like**
19+
<!--- A description of what you want to happen. -->
1520

1621
**Describe alternatives you've considered**
17-
A description of any alternative solutions or features you've considered.
22+
<!--- A description of any alternative solutions or features you've considered. -->
23+
24+
**Contribution Intention (Optional)**
25+
<!--- If the feature request is accepted, would you be willing to submit a PR?
26+
* If yes, please follow https://github.com/kubernetes-sigs/aws-load-balancer-controller/blob/main/CONTRIBUTING.md to start your contribution
27+
* If you're not able to contribute this feature, it will be open for public contribution. Feature requests are prioritized by the number of upvotes. We encourage community participation to help implement features faster.
28+
-->
29+
-[ ] Yes, I am willing to contribute a PR to implement this feature
30+
-[ ] No, I cannot work on a PR at this time

0 commit comments

Comments
 (0)
Please sign in to comment.