Merge remote-tracking branch 'origin/master'

.github/ISSUE_TEMPLATE/ask-for-help.md

@@ -12,6 +12,8 @@ Please search in Issues without filters: https://github.com/louislam/uptime-kuma
 **Info**
 Uptime Kuma Version:
 Using Docker?: Yes/No
+Docker Version:
+Node.js Version (Without Docker only):
 OS:
 Browser:
 

.github/ISSUE_TEMPLATE/bug_report.md

@@ -25,10 +25,13 @@ A clear and concise description of what you expected to happen.
 
 
 **Info**
-- Uptime Kuma Version:
+Uptime Kuma Version:
-- Using Docker?: Yes/No
+Using Docker?: Yes/No
-- OS: 
+Docker Version:
-- Browser:
+Node.js Version (Without Docker only):
+OS:
+Browser:
+
 
 **Screenshots**
 If applicable, add screenshots to help explain your problem.
@@ -36,3 +39,6 @@ If applicable, add screenshots to help explain your problem.
 **Error Log**
 It is easier for us to find out the problem.
 
+Docker: "docker logs <container id>"
+PM2: "~/.pm2/logs/"  (e.g. /home/ubuntu/.pm2/logs)
+

kubernetes/README.md

@@ -1,4 +1,7 @@
 # Uptime-Kuma K8s Deployment
+
+⚠ Warning: K8s deployment is provided by contributors. I have no experience with K8s and I can't fix error in the future. I only test Docker and Node.js. Use at your own risk.
+
 ## How does it work?
 
 Kustomize is a tool which builds a complete deployment file for all config elements.
@@ -25,4 +28,4 @@ This ingressroute.yml is for the [nginx-ingress-controller](https://kubernetes.g
 - run ```kustomize build > apply.yml```
 - run ```kubectl apply -f apply.yml```
 
-Now you should see some k8s magic and Uptime-Kuma should be available at the specified address.
+Now you should see some k8s magic and Uptime-Kuma should be available at the specified address.

kubernetes/uptime-kuma/deployment.yml

@@ -30,6 +30,9 @@ spec:
               command:
                 - node
                 - extra/healthcheck.js
+            initialDelaySeconds: 180
+            periodSeconds: 60
+            timeoutSeconds: 30
           readinessProbe:
             httpGet:
               path: /