add template note to file network policy issues against the correct r…

…epo (#2631)

.github/ISSUE_TEMPLATE/bug-report.md

@@ -11,12 +11,14 @@ assignees: ''
 For urgent operational issues, please contact AWS Support directly at https://aws.amazon.com/premiumsupport/
 
 If you think you have found a potential security issue, please do not post it as an issue. Instead, follow the instructions at https://aws.amazon.com/security/vulnerability-reporting/ or email AWS Security directly at [email protected]
+
+For Network Policy issues, please file at https://github.com/aws/aws-network-policy-agent/issues
 -->
 
 **What happened**:
 <!--
- Include log lines if possible
- -->
+Include log lines if possible
+-->
 
 **Attach logs**
 <!--

.github/ISSUE_TEMPLATE/enhancement.md

@@ -12,7 +12,10 @@ For urgent operational issues, please contact AWS Support directly at https://aw
 
 If you think you have found a potential security issue, please do not post it as an issue. Instead, follow the instructions at https://aws.amazon.com/security/vulnerability-reporting/ or email AWS Security directly at [email protected]
 
-Please only use this template for submitting enhancement requests -->
+For Network Policy enhancements, please file at https://github.com/aws/aws-network-policy-agent/issues
+
+Please only use this template for submitting enhancement requests.
+-->
 
 **What would you like to be added**:
 

.github/ISSUE_TEMPLATE/support-request.md

@@ -11,14 +11,16 @@ assignees: ''
 For urgent operational issues, please contact AWS Support directly at https://aws.amazon.com/premiumsupport/
 
 If you think you have found a potential security issue, please do not post it as an issue. Instead, follow the instructions at https://aws.amazon.com/security/vulnerability-reporting/ or email AWS Security directly at [email protected]
+
+For Network Policy requests, please file at https://github.com/aws/aws-network-policy-agent/issues
 -->
 
 **What happened**:
 
 <!--
-If you're looking for help, check the [troubleshooting guide](https://github.com/aws/amazon-vpc-cni-k8s/blob/master/docs/troubleshooting.md)
+If you are looking for help, check the [troubleshooting guide](https://github.com/aws/amazon-vpc-cni-k8s/blob/master/docs/troubleshooting.md)
 
-If you're unable to find the answers and would like to create an issue, upload the logs by running [CNI Log Collection tool](https://docs.aws.amazon.com/eks/latest/userguide/troubleshooting.html#troubleshoot-cni) and email the log archive to [email protected]
+If you are unable to find the answers and would like to create an issue, upload the logs by running [CNI Log Collection tool](https://docs.aws.amazon.com/eks/latest/userguide/troubleshooting.html#troubleshoot-cni) and email the log archive to [email protected]
 -->
 
 **Environment**:

.github/PULL_REQUEST_TEMPLATE.md

@@ -3,12 +3,11 @@
 2. Ensure you have included output of manual testing done in the Testing section.
 3. Ensure number of lines of code for new or existing methods are within the reasonable limit.
 4. Ensure your change works on existing clusters after upgrade.
-5. If your mounting any new file or directory, make sure its not opening up any security attack vector for aws-vpc-cni-k8s modules.
-6. If AWS apis are invoked, document the call rate in the description section.
+5. If you are mounting any new file or directory, make sure it is not opening up any security attack vector for aws-vpc-cni-k8s modules.
+6. If AWS APIs are invoked, document the call rate in the description section.
 7. If EC2 Metadata apis are invoked, ensure to handle stale information returned from metadata.
 -->
 **What type of PR is this?**
-
 <!--
 Add one of the following:
 bug
@@ -32,18 +31,12 @@ output of manual testing/integration tests results and also attach logs
 showing the fix being resolved
 -->
 
-**Automation added to e2e**:
-<!-- 
-Test case added to lib/integration.sh 
-If no, create an issue with enhancement/testing label
--->
-
 **Will this PR introduce any new dependencies?**:
 <!-- 
 e.g. new EC2/K8s API, IMDS API, dependency on specific kernel module/version or binary in container OS.
 -->
 
-**Will this break upgrades or downgrades. Has updating a running cluster been tested?**:
+**Will this break upgrades or downgrades? Has updating a running cluster been tested?**:
 
 
 **Does this change require updates to the CNI daemonset config files to work?**: