Fix ingress (#433)

* Fix ingress

* Update readme

Author: vcarl

README.md

@@ -79,6 +79,7 @@ Run a docker build, tag it, and push to the registry. We need to retrieve the im
 ```sh
 docker build . -t <your gh>/reactibot:test
 docker tag $(docker images <your gh>/reactibot:test | tr -s ' ' | cut -f3 -d' ' | tail -n 1) ghcr.io/<your gh>/reactibot:test
+docker push ghcr.io/<your gh>/reactibot:test
 ```
 
 Run a local deploy.

cluster/ingress.yaml

@@ -3,9 +3,14 @@ kind: Ingress
 metadata:
   name: reactibot-ingress
   annotations:
-    nginx.ingress.kubernetes.io/rewrite-target: /
-    cert-manager.io/cluster-issuer: letsencrypt-prod # Optional, for TLS
+    nginx.ingress.kubernetes.io/ssl-redirect: "true"
+    nginx.ingress.kubernetes.io/force-ssl-redirect: "true"
+    nginx.ingress.kubernetes.io/hsts: "true"
+    nginx.ingress.kubernetes.io/hsts-max-age: "31536000"
+    nginx.ingress.kubernetes.io/hsts-include-subdomains: "true"
+    cert-manager.io/cluster-issuer: letsencrypt-prod
 spec:
+  ingressClassName: nginx
   rules:
     - host: api.reactiflux.com
       http:
@@ -14,10 +19,10 @@ spec:
             pathType: Prefix
             backend:
               service:
-                name: reactibot
+                name: reactibot-service
                 port:
                   number: 80
   tls:
     - hosts:
         - api.reactiflux.com
-      secretName: my-tls-secret # Used for HTTPS
+      secretName: reactibot-tls-cert