-
egon w. stemle authored
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
egon w. stemle authoredSo 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