From bf9342e95c8211ebbda6b357ea0048d5283a1bf2 Mon Sep 17 00:00:00 2001 From: Carlos Eduardo Date: Wed, 28 Oct 2020 16:39:42 -0300 Subject: [PATCH] Update bug_report.md --- .github/ISSUE_TEMPLATE/bug_report.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md index e26f725..53c084a 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.md +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -14,9 +14,10 @@ A clear and concise description of what the bug is. Please do not use an Issue t 1. Which kind of Kubernetes cluster are you using? (Kubernetes, K3s, etc) 2. Are all pods in "Running" state? If any is in CrashLoopback or Error, check it's logs. -2. You cluster already works with other applications that have HTTP/HTTPS? If not, first deploy an example NGINX and test it's access thru the created URL. -3. If you enabled persistence, do your cluster already provides persistent storage (PVs) to other applications? -4. Does it provides dynamic storage thru StorageClass? +3. You cluster already works with other applications that have HTTP/HTTPS? If not, first deploy an example NGINX and test it's access thru the created URL. +4. If you enabled persistence, do your cluster already provides persistent storage (PVs) to other applications? +5. Does it provides dynamic storage thru StorageClass? +6. If you deployed the monitoring stack and some targets are not available or showing no metrics in Grafana, make sure you don't have IPTables rules or use a firewall on your nodes before deploying Kubernetes. **Customizations**