Add failing/flaking-test templates to the repository

Author: furkatgofurov7

.github/ISSUE_TEMPLATE/failing-test.md

@@ -0,0 +1,26 @@
+---
+name: 🚨 Failing Test
+about: Report continuously failing tests or jobs in Cluster API CI
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+<!-- Please only use this template for submitting reports about continuously failing tests or jobs in Cluster API CI -->
+
+**Which jobs are failing:**
+
+**Which tests are failing:**
+
+**Since when has it been failing:**
+
+**Testgrid link:**
+
+**Reason for failure (if possible):**
+
+**Anything else we need to know:**
+
+/kind failing-test
+
+[One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels]

.github/ISSUE_TEMPLATE/flaking-test.md

@@ -0,0 +1,27 @@
+---
+name: ❄️ Flaking Test
+about: Report flaky tests or jobs in Cluster API CI
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+<!-- Please only use this template for submitting reports about flaky tests or jobs (pass or fail with no underlying change in code) in Cluster API CI -->
+
+**Which jobs are flaking:**
+
+**Which tests are flaking:**
+
+**Testgrid link:**
+
+**Reason for failure (if possible):**
+
+**Anything else we need to know:**
+- links to go.k8s.io/triage appreciated
+- links to specific failures in spyglass appreciated
+
+
+/kind flake
+
+[One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels]

docs/release/release-tasks.md

@@ -383,8 +383,9 @@ The goal of this task is to keep our tests running in CI stable.
 1. Add yourself to the [Cluster API alert mailing list](https://github.com/kubernetes/k8s.io/blob/151899b2de933e58a4dfd1bfc2c133ce5a8bbe22/groups/sig-cluster-lifecycle/groups.yaml#L20-L35)
     <br\>**Note**: An alternative to the alert mailing list is manually monitoring the [testgrid dashboards](https://testgrid.k8s.io/sig-cluster-lifecycle-cluster-api)
     (also dashboards of previous releases). Using the alert mailing list has proven to be a lot less effort though.
-2. Triage CI failures reported by mail alerts or found by monitoring the testgrid dashboards:
-    1. Create an issue in the Cluster API repository to surface the CI failure.
+2. Check the existing **failing-test** and **flaking-test** issue templates under `.github/ISSUE_TEMPLATE/` folder of the repo, used to create an issue for failing or flaking tests respectively. Please make sure they are up-to-date and if not, send a PR to update or improve them.
+3. Triage CI failures reported by mail alerts or found by monitoring the testgrid dashboards:
+    1. Create an issue using an appropriate template (failing-test) in the Cluster API repository to surface the CI failure.
     2. Identify if the issue is a known issue, new issue or a regression.
     3. Mark the issue as `release-blocking` if applicable.
 
@@ -398,7 +399,7 @@ To reduce the amount of flakes please periodically:
     * [periodic-cluster-api-e2e-mink8s-main](https://storage.googleapis.com/k8s-triage/index.html?pr=1&job=periodic-cluster-api-e2e-mink8s-main)
     * [periodic-cluster-api-test-main](https://storage.googleapis.com/k8s-triage/index.html?pr=1&job=periodic-cluster-api-test-main)
     * [periodic-cluster-api-test-mink8s-main](https://storage.googleapis.com/k8s-triage/index.html?pr=1&job=periodic-cluster-api-test-mink8s-main)
-3. Open issues for occurring flakes and ideally fix them or find someone who can.
+2. Open issues using an appropriate template (flaking-test) for occurring flakes and ideally fix them or find someone who can.
    **Note**: Given resource limitations in the Prow cluster it might not be possible to fix all flakes.
    Let's just try to pragmatically keep the amount of flakes pretty low.