So far, we have used TLS certs from eurac's IT. Now, we (re-)use k8s
infrastructure (in particular the kube-lego add-on) and let kube-lego
- request/renew TLS certificates
- manage the certificate within a k8s secret
We then make this k8s secret available to our nginx and configure nginx
to use it.

We also got rid of internal TLS communication between ingress and the
apps avoiding the necessity to (re-)create valid/self-signed certs. The
overhead seemed unnecessary.

Note: using HTTP(!) over port 443 for internal communication (Shibboleth mishap)

Fix #62

'502 Bad Gateway' errors from the k8s ingress server can be solved
(sometimes) by restarting the nginx pod. Here we check
https://clarin(-dev).eurac.edu:443

Addresses #53

fixed.

- bumped version numbers to 1.0

- bumped version number in kube deploy

files