feat: add pull request and issue templates to this repository.

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,51 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: '[BUG]'
+labels: 'kind/bug'
+assignees: ''
+
+---
+
+### Rancher Server Setup
+- Rancher version:
+- Installation option (Docker install/Helm Chart):
+   - If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc):
+- Proxy/Cert Details:
+
+### Information about the Cluster
+- Kubernetes version:
+- Cluster Type (Local/Downstream):
+   - If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider):
+<!--
+* Custom = Running a docker command on a node
+* Imported = Running kubectl apply onto an existing k8s cluster
+* Hosted = EKS, GKE, AKS, etc
+ * Infrastructure Provider = Rancher provisioning the nodes using different node drivers (e.g. AWS, Digital Ocean, etc)
+-->
+
+### User Information
+- What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)
+  - If custom, define the set of permissions:
+
+### Provider Information
+- What is the version of the Rancher v2 Terraform Provider in use?
+- What is the version of Terraform in use?
+
+### Describe the bug
+<!--A clear and concise description of what the bug is.-->
+
+### To Reproduce
+<!--Steps to reproduce the behavior-->
+
+### Actual Result
+<!-- A clear and concise description of what actually happened. -->
+
+### Expected Result
+<!--A clear and concise description of what you expected to happen.-->
+
+### Screenshots
+<!-- If applicable, add screenshots to help explain your problem.-->
+
+### Additional context
+<!--Add any other context about the problem here.-->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,20 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: '[RFE] '
+labels: 'enhancement'
+assignees: ''
+
+---
+
+### Is your feature request related to a problem? Please describe.
+<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
+
+### Describe the solution you'd like
+<!-- A clear and concise description of what you want to happen. -->
+
+### Describe alternatives you've considered
+<!-- A clear and concise description of any alternative solutions or features you've considered. -->
+
+### Additional context
+<!-- Add any other context or screenshots about the feature request here. -->

.github/pull_request_template.md

@@ -0,0 +1,23 @@
+## Issue: <!-- link the issue or issues this PR resolves here -->
+<!-- If your PR depends on changes from another pr link them here and describe why they are needed in your solution section. -->
+
+## Problem
+<!-- Describe the root cause of the issue you are resolving. This may include what behavior is observed and why it is not desirable. If this is a new feature describe why we need this feature and how it will be used. -->
+## Solution
+<!-- Describe what you changed to fix the issue. Relate your changes back to the original issue / feature and explain how this addresses the issue. -->
+
+## Testing
+<!-- Note: Confirm if the repro steps in the GitHub issue are valid, if not, please update the issue with accurate repro steps. -->
+
+## Engineering Testing
+### Manual Testing
+<!-- Describe what manual testing you did (if no testing was done, explain why). -->
+
+### Automated Testing
+<!--If you added/updated unit/integration/validation tests, describe what cases they cover and do not cover. -->
+
+## QA Testing Considerations
+<!-- Highlight areas or (additional) cases that QA should test w.r.t a fresh install as well as the upgrade scenarios -->
+
+### Regressions Considerations
+<!-- Dedicated section to specifically call out any areas that with higher chance of regressions caused by this change, include estimation of probability of regressions -->