add issue template

.github/ISSUE_TEMPLATE/bug-report.md

@@ -0,0 +1,41 @@
+---
+name: Bug Report
+about: Template for bug reports
+labels: kind/bug
+---
+
+# Expected Behavior
+
+# Actual Behavior
+
+# Steps to Reproduce the Problem
+
+1.
+2.
+3.
+
+# Additional Info
+
+- Kubernetes version:
+
+  **Output of `kubectl version`:**
+
+  ```
+  (paste your output here)
+  ```
+
+- kube-ovn version:
+
+  ```
+  (paste your output here)
+  ```
+
+- operation-system/kernel version:
+
+  **Output of `awk -F '=' '/PRETTY_NAME/ { print $2 }' /etc/os-release`:**
+  **Output of `uname -r`:**
+  ```
+  (paste your output here)
+  ```
+
+<!-- Any other additional information -->

.github/ISSUE_TEMPLATE/feature-request.md

@@ -0,0 +1,13 @@
+---
+name: Feature Request
+about: Template for feature requests
+labels: kind/feature
+---
+
+### Feature request
+
+<!-- Please describe the feature request and why you would like to have it -->
+
+### Use case
+
+<!-- Please add a concrete use case to demonstrate how such a feature would add value for the user. If you don't have a use case for your feature, please remove this section (however providing a good use case increases the likelihood to be picked up) -->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,19 @@
+#### What type of this PR
+Examples of user facing changes:
+- API changes
+- Bug fixes
+<!-- 
+Describe your changes here- ideally you can get that description straight from your descriptive commit message(s)! 
+
+In addition, categorize the changes you're making using the "/kind" Prow command, example:
+
+/kind <kind>
+
+Supported kinds are: bug, cleanup, design, documentation, failing-test, feature, flake, misc, question, tep
+-->
+
+#### Which issue(s) this PR fixes:
+Fixes #(issue-number)
+
+
+